FKIE_CVE-2025-48069
Vulnerability from fkie_nvd - Published: 2025-05-21 18:15 - Updated: 2026-06-17 09:29| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "ejson2env",
"vendor": "Shopify",
"versions": [
{
"status": "affected",
"version": "\u003c 2.0.8"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "ejson2env allows users to decrypt EJSON secrets and export them as environment variables. Prior to version 2.0.8, the `ejson2env` tool has a vulnerability related to how it writes to `stdout`. Specifically, the tool is intended to write an export statement for environment variables and their values. However, due to inadequate output sanitization, there is a potential risk where variable names or values may include malicious content, resulting in additional unintended commands being output to `stdout`. If this output is improperly utilized in further command execution, it could lead to command injection, allowing an attacker to execute arbitrary commands on the host system. Version 2.0.8 sanitizes output during decryption. Other mitigations involve avoiding use of `ejson2env` to decrypt untrusted user secrets and/or avoiding evaluating or executing the direct output from `ejson2env` without removing nonprintable characters."
},
{
"lang": "es",
"value": "ejson2env permite a los usuarios descifrar secretos EJSON y exportarlos como variables de entorno. Antes de la versi\u00f3n 2.0.8, la herramienta `ejson2env` presentaba una vulnerabilidad relacionada con la escritura en `stdout`. Espec\u00edficamente, la herramienta est\u00e1 dise\u00f1ada para escribir una declaraci\u00f3n de exportaci\u00f3n para las variables de entorno y sus valores. Sin embargo, debido a una depuraci\u00f3n de salida inadecuada, existe el riesgo de que los nombres o valores de las variables incluyan contenido malicioso, lo que resulta en la salida de comandos no deseados adicionales a `stdout`. Si esta salida se utiliza incorrectamente en la ejecuci\u00f3n posterior de comandos, podr\u00eda provocar una inyecci\u00f3n de comandos, lo que permite a un atacante ejecutar comandos arbitrarios en el sistema host. La versi\u00f3n 2.0.8 limpia la salida durante el descifrado. Otras mitigaciones incluyen evitar el uso de `ejson2env` para descifrar secretos de usuario no confiables o evitar evaluar o ejecutar la salida directa de `ejson2env` sin eliminar caracteres no imprimibles."
}
],
"id": "CVE-2025-48069",
"lastModified": "2026-06-17T09:29:06.093",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.6,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 0.7,
"impactScore": 5.9,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-48069",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-05-21T18:17:11.496534Z",
"version": "2.0.3"
}
}
]
},
"published": "2025-05-21T18:15:53.550",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/Shopify/ejson2env/commit/592b3ceea967fee8b064e70983e8cec087b6d840"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/Shopify/ejson2env/security/advisories/GHSA-2c47-m757-32g6"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-78"
}
],
"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.