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.
The vulnerability exists because environment variables are not properly sanitized during the decryption phase, which enables malicious keys or encrypted values to inject commands.
An attacker with control over .ejson
files can inject commands in the environment where source $(ejson2env)
or eval ejson2env
are executed.
ejson2env
that sanitizes the output during decryption orejson2env
to decrypt untrusted user secrets orejson2env
without removing nonprintable characters.Thanks to security researcher Demonia for reporting this issue.
{ "nvd_published_at": "2025-05-21T18:15:53Z", "cwe_ids": [ "CWE-78" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2025-05-21T18:32:37Z" }