Advisory

GHSA-2c47-m757-32g6

Also known as: CVE-2025-48069, GO-2025-3702

Summary

Insufficient input sanitization in ejson2env

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-05-21 18:32 UTC
Modified
2025-05-27 19:26 UTC

Affected packages and fixes

github.com/Shopify/ejson2env/v2

Go · All systems

Affected

  • introduced 0, fixed 2.0.8 (semver)

Fixed versions

2.0.8

Fix

ejson2env

RubyGems · All systems

Affected

  • introduced 0, fixed 2.0.8 (ecosystem)

Fixed versions

2.0.8

Fix

The export has no generic command for this ecosystem.

github.com/Shopify/ejson2env

Go · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences