Memory Exposure in tunnel-agent
Priority LOW 38CWE-200Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-200.
Summary
Versions of `tunnel-agent` before 0.6.0 are vulnerable to memory exposure. This is exploitable if user supplied input is provided to the auth value and is a number. Proof-of-concept: ```js require('request')({ method: 'GET', uri: 'http://www.example.com', tunnel: true, proxy:{ protocol: 'http:', host:'127.0.0.1', port:8080, auth:USERSUPPLIEDINPUT // number } }); ``` ## Recommendation Update to version 0.6.0 or later.
Why it matters now
Fix Fixed tunnel-agent (npm): 0.6.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | tunnel-agent (npm) | before 0.6.0 | 0.6.0 | Patch available | GHSA-xc7v-wxcw-j472 |
- tunnel-agent (npm) Vendor— Affected before 0.6.0 Fixed in 0.6.0 Patch available GHSA-xc7v-wxcw-j472
Remediation
- Fix · GHSA-xc7v-wxcw-j472 tunnel-agent (npm) Fixed in 0.6.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-xc7v-wxcw-j472
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences