FKIE_CVE-2025-27137
Vulnerability from fkie_nvd - Published: 2025-02-24 21:15 - Updated: 2026-06-17 09:03| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "dependency-track",
"vendor": "DependencyTrack",
"versions": [
{
"status": "affected",
"version": "\u003c 4.12.6"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Dependency-Track is a component analysis platform that allows organizations to identify and reduce risk in the software supply chain. Dependency-Track allows users with the `SYSTEM_CONFIGURATION` permission to 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. Prior to version 4.12.6, users of Dependency-Track with the `SYSTEM_CONFIGURATION` permission can abuse the `include` tag by crafting notification templates that `include` sensitive 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 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. As a workaround, avoid assigning the `SYSTEM_CONFIGURATION` permission to untrusted users. 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."
},
{
"lang": "es",
"value": "Dependency-Track es una plataforma de an\u00e1lisis de componentes que permite a las organizaciones identificar y reducir el riesgo en la cadena de suministro de software. Dependency-Track permite a los usuarios con el permiso `SYSTEM_CONFIGURATION` personalizar las plantillas de notificaci\u00f3n. Las plantillas se eval\u00faan utilizando el motor de plantillas Pebble. Pebble admite una etiqueta `include`, que permite a los autores de plantillas incluir el contenido de archivos arbitrarios en la evaluaci\u00f3n. Antes de la versi\u00f3n 4.12.6, los usuarios de Dependency-Track con el permiso `SYSTEM_CONFIGURATION` pod\u00edan abusar de la etiqueta `include` creando plantillas de notificaci\u00f3n que `incluyen` archivos locales confidenciales, como `/etc/passwd` o `/proc/1/environ`. Al configurar una plantilla de este tipo para una regla de notificaci\u00f3n (tambi\u00e9n conocida como \"Alerta\") y hacer que env\u00ede notificaciones a un destino controlado por el actor, se puede filtrar informaci\u00f3n confidencial. El problema se ha solucionado en Dependency-Track 4.12.6. En las versiones corregidas, la etiqueta `include` ya no se puede utilizar. El uso de la etiqueta provocar\u00e1 un error en la evaluaci\u00f3n de la plantilla. Como workaround, evite asignar el permiso `SYSTEM_CONFIGURATION` a usuarios que no sean de confianza. El permiso `SYSTEM_CONFIGURATION` de forma predeterminada solo se otorga a los miembros del equipo `Administradores`. Asignar este permiso a usuarios o equipos que no sean administradores es un riesgo de seguridad en s\u00ed mismo y se desaconseja enf\u00e1ticamente."
}
],
"id": "CVE-2025-27137",
"lastModified": "2026-06-17T09:03:04.877",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 4.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 0.8,
"impactScore": 3.6,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-27137",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-02-25T14:34:43.617875Z",
"version": "2.0.3"
}
}
]
},
"published": "2025-02-24T21:15:11.213",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/DependencyTrack/dependency-track/pull/4684"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/DependencyTrack/dependency-track/pull/4685"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/DependencyTrack/dependency-track/security/advisories/GHSA-9582-88hr-54w3"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/JLLeitschuh/security-research/security/advisories/GHSA-p75g-cxfj-7wrx"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/PebbleTemplates/pebble/issues/680"
},
{
"source": "security-advisories@github.com",
"url": "https://pebbletemplates.io/wiki/tag/include"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-73"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.