ejson2env has insufficient input sanitization
Shopify ejson2env
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/Shopify/ejson2env/v2 Go |
|
|
| ejson2env RubyGems |
|
|
| github.com/Shopify/ejson2env Go |
Shopify ejson2env
| Product | Affected | Fixed in |
|---|---|---|
| github.com/Shopify/ejson2env/v2 Go |
|
|
| ejson2env RubyGems |
|
|
| github.com/Shopify/ejson2env Go |
all versions| No fix yet |
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.
From the CVE record · GitHub_M
ejson2env can write unintended commands to stdout when decrypted variable names or values contain malicious content. An attacker who can supply those secrets may execute commands on the host if the output is subsequently evaluated or executed; the input does not specify an authentication requirement or network access.
Check installations of Go github.com/Shopify/ejson2env/v2 and RubyGems ejson2env before 2.0.8, and all versions of the unversioned Go github.com/Shopify/ejson2env package.