github.com/Shopify/ejson2env/v2
Affected
- introduced
0, fixed2.0.8(semver)
Fixed versions
2.0.8
Fix
- Fixed version
2.0.8go get github.com/Shopify/ejson2env/[email protected]
Advisory
Also known as: CVE-2025-48069, GO-2025-3702
Insufficient input sanitization in ejson2env
Summary
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 vulnerabilities, allowing an attacker to execute arbitrary commands on the host system.
Details
The vulnerability exists because environment variables are not properly sanitized during the decryption phase, which enables malicious keys or encrypted values to inject commands.
Impact
An attacker with control over .ejson files can inject commands in the environment where source $(ejson2env) or eval ejson2env are executed.
Mitigation
ejson2env that sanitizes the output during decryption orejson2env to decrypt untrusted user secrets orejson2env without removing nonprintable characters.Credit
Thanks to security researcher Demonia for reporting this issue.
Medium Basis: The source's own band: MODERATE
0, fixed 2.0.8 (semver)2.0.8
2.0.8go get github.com/Shopify/ejson2env/[email protected]0, fixed 2.0.8 (ecosystem)2.0.8
The export has no generic command for this ecosystem.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0