p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in @dependencytrack/frontend

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für @dependencytrack/frontend: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 2

  1. CVE-2025-64758

    Mittel · CVSS 4.8EPSS 0,24%Korrektur verfügbar

    @dependencytrack/frontend Vulnerable to Persistent Cross-Site-Scripting via Welcome Message

    @dependencytrack/frontend is a Single Page Application (SPA) used in Dependency-Track, an open source Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Since version 4.12.0, Dependency-Track users with the SYSTEM_CONFIGURATION permission can configure a "welcome message", which is HTML that is to be rendered on the login page for branding purposes. When rendering the welcome message, Dependency-Track versions before 4.13.6 did not properly sanitize the HTML, allowing arbitrary JavaScript to be executed. Users with the SYSTEM_CONFIGURATION permission (i.e., administrators), can expl

    • Auf 4.13.6 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2022-39350

    Mittel · CVSS 5.4EPSS 0,88%Korrektur verfügbar

    @dependencytrack/frontend vulnerable to Persistent Cross-Site-Scripting via Vulnerability Details

    @dependencytrack/frontend is a Single Page Application (SPA) used in Dependency-Track, an open source Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Due to the common practice of providing vulnerability details in markdown format, the Dependency-Track frontend renders them using the JavaScript library Showdown. Showdown does not have any XSS countermeasures built in, and versions before 4.6.1 of the Dependency-Track frontend did not encode or sanitize Showdown's output. This made it possible for arbitrary JavaScript included in vulnerability details via HTML attributes to be exe

    • Auf 4.6.1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →