GHSA-97rm-xj73-33jh is a high-severity (CVSS 8.3) CWE-15 vulnerability in ebay-mcp. O3 Security confirms whether GHSA-97rm-xj73-33jh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
eBay API MCP Server Affected by Environment Variable Injection
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
ebay-mcpnpmDescription
The ebay_set_user_tokens tool allows updating the .env file with new tokens. The updateEnvFile function in src/auth/oauth.ts blindly appends or replaces values without validating them for newlines or quotes. This allows an attacker to inject arbitrary environment variables into the configuration file.
Impact
An attacker can inject arbitrary environment variables into the .env file. This could lead to:
- Configuration Overwrites: Attackers can overwrite critical settings like
EBAY_REDIRECT_URIto hijack OAuth flows. - Denial of Service: Injecting invalid configuration can prevent the server from starting.
- Potential RCE: In some environments, controlling environment variables (like
NODE_OPTIONS) can lead to Remote Code Execution.
Found with MCPwner 🕶
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | ebay-mcp | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ebay-mcp. 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.
Remediation status
No patched version of ebay-mcp has shipped for GHSA-97rm-xj73-33jh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-97rm-xj73-33jh 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-97rm-xj73-33jh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-97rm-xj73-33jh in your dependencies?
O3 detects GHSA-97rm-xj73-33jh across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.