GHSA-xc7v-wxcw-j472 Memory Exposure in tunnel-agent
Not scored
Published
Check this codebase for GHSA-xc7v-wxcw-j472 and fix it if it is affected.
What it is: GHSA-xc7v-wxcw-j472 is a vulnerability in tunnel-agent, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-xc7v-wxcw-j472 in the wild and no public exploit code.
Affected packages and fixed versions:
- tunnel-agent (npm): affected all versions; fixed in 0.6.0
- tunnel-agent (npm): affected all versions; fixed in 0.6.0
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/GHSA-xc7v-wxcw-j472/ (Markdown: https://insights.sbomify.com/GHSA-xc7v-wxcw-j472/index.md)
An attacker can expose memory contents by supplying numeric input to the proxy authentication value in tunnel-agent.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-xc7v-wxcw-j472?
GHSA-xc7v-wxcw-j472 is a vulnerability in tunnel-agent, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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:
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.
Which versions are affected by GHSA-xc7v-wxcw-j472?
2 open source packages ship an affected version, including tunnel-agent.
| Package | Affected | Fixed in |
|---|---|---|
tunnel-agent npm | All versions | 0.6.0 |
tunnel-agent npm | All versions | 0.6.0 |
How do I fix GHSA-xc7v-wxcw-j472?
Upgrade tunnel-agent to 0.6.0 or later.
Is GHSA-xc7v-wxcw-j472 being exploited?
There is no known exploitation of GHSA-xc7v-wxcw-j472 in the wild and no public exploit code.