Skip to content

Local file inclusion via custom notification templates

Moderate
nscuro published GHSA-9582-88hr-54w3 Feb 24, 2025

Package

maven org.dependencytrack:dependency-track (Maven)

Affected versions

< 4.12.6

Patched versions

4.12.6

Description

Description

Users with the SYSTEM_CONFIGURATION permission can customize notification templates. Templates are evaluated using the Pebble template engine. Pebble supports an include tag, which allows template authors to include the content of arbitrary files upon evaluation.

Impact

Actors with the SYSTEM_CONFIGURATION permission can craft notification templates that include local files, such as /etc/passwd or /proc/1/environ. By configuring such a template for a notification rule (aka "Alert"), and having it send notifications to a destination controlled by the actor, sensitive information may be leaked.

The SYSTEM_CONFIGURATION permission per default is only granted to members of the Administrators team. Assigning this permission to non-administrative users or teams is a security risk in itself, and highly discouraged.

Patches

The issue has been fixed in Dependency-Track 4.12.6.

In fixed versions, the include tag can no longer be used. Usage of the tag will cause template evaluation to fail.

References

Credit

Thanks to Jonathan Leitschuh for finding and responsibly disclosing the issue.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

CVE ID

CVE-2025-27137

Weaknesses

Credits