How severe is GHSA-2c47-m757-32g6?

GHSA-2c47-m757-32g6 has a CVSS score of 6.6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2c47-m757-32g6?

GHSA-2c47-m757-32g6 affects the following packages: github.com/Shopify/ejson2env/v2 (Go), github.com/Shopify/ejson2env (Go), ejson2env (RubyGems). Ecosystems affected: Go, RubyGems.

How do I fix GHSA-2c47-m757-32g6?

Update github.com/Shopify/ejson2env/v2 to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2c47-m757-32g6 is resolved across your whole dependency graph.

How do I detect GHSA-2c47-m757-32g6 in my Go, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Shopify/ejson2env/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2c47-m757-32g6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2c47-m757-32g6?

O3 pinpoints whether GHSA-2c47-m757-32g6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2c47-m757-32g6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2c47-m757-32g6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2c47-m757-32g6?

GHSA-2c47-m757-32g6 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2c47-m757-32g6?

GHSA-2c47-m757-32g6 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-2c47-m757-32g6 published, and has it been updated?

GHSA-2c47-m757-32g6 was published on May 21, 2025 and was last updated on May 27, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go💎 RubyGems

GHSA-2c47-m757-32g6

MEDIUM

Insufficient input sanitization in ejson2env

Also known asCVE-2025-48069GO-2025-3702

Published

May 21, 2025

Updated

May 27, 2025

Affected

3 pkgs

Patched

2 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk68th percentile+0.69%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

🐹github.com/Shopify/ejson2env/v2🐹github.com/Shopify/ejson2env💎ejson2env

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go, RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/Shopify/ejson2env/v2`	all versions	2.0.8
🐹Go	`github.com/Shopify/ejson2env`	all versions	No fix
💎RubyGems	`ejson2env`	all versions	2.0.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Shopify/ejson2env/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/Shopify/ejson2env/v2 to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2c47-m757-32g6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2c47-m757-32g6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2c47-m757-32g6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ###

O3 Security · Impact-Aware SCA

Is GHSA-2c47-m757-32g6 in your dependencies?

O3 detects GHSA-2c47-m757-32g6 across Go, RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works