NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-48069: Insufficient input sanitization in ejson2env

mediumCVSS 3.1 6.6GHSA-2c47-m757-32g6

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.

Published May 21, 2025 · Updated May 27, 2025

Affected packages

github.com/Shopify/ejson2env/v2

Ecosystem
Go
Affected
< 2.0.8
Fixed in
2.0.8
Check
go list -m github.com/Shopify/ejson2env/v2

ejson2env

Ecosystem
RubyGems
Affected
< 2.0.8
Fixed in
2.0.8
Check
bundle info ejson2env

github.com/Shopify/ejson2env

Ecosystem
Go
Affected
< 2.0.8
Fixed in
No patched version yet
Check
go list -m github.com/Shopify/ejson2env

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

  • Update to a version of ejson2env that sanitizes the output during decryption or
  • Do not use ejson2env to decrypt untrusted user secrets or
  • Do not evaluate or execute the direct output from ejson2env without removing nonprintable characters.

Credit

Thanks to security researcher Demonia for reporting this issue.

Credited to thepwagner, alexhope61, rj-coleman, Owen-Cummings.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology