forked from snyk-labs/nodejs-goof
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No CVE - medium detected in tunnel-agent #222
Comments
auto-closed by |
This was referenced Sep 24, 2022
This was referenced Sep 26, 2022
This was referenced Sep 29, 2022
This was referenced Oct 3, 2022
This was referenced Oct 5, 2022
This was referenced Jan 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Package Name: tunnel-agent
Package Version: ['0.4.3']
Package Manager: npm
Target File: package.json
Severity Level: medium
Snyk ID: npm:tunnel-agent:20170305
Snyk CVE: No CVE
Snyk CWE: CWE-201
Link to issue in Snyk: https://app.snyk.io/org/rhicksiii91/project/93ddcac2-4d2c-43e7-b383-b47b30846d11
Snyk Description: ## Overview
tunnel-agent
is HTTP proxy tunneling agent. Affected versions of the package are vulnerable to Uninitialized Memory Exposure.A possible memory disclosure vulnerability exists when a value of type
number
is used to set the proxy.auth option of a requestrequest
and results in a possible uninitialized memory exposures in the request body.This is a result of unobstructed use of the
Buffer
constructor, whose insecure default constructor increases the odds of memory leakage.Details
Constructing a
Buffer
class with integerN
creates aBuffer
of lengthN
with raw (not "zero-ed") memory.In the following example, the first call would allocate 100 bytes of memory, while the second example will allocate the memory needed for the string "100":
tunnel-agent
'srequest
construction uses the defaultBuffer
constructor as-is, making it easy to append uninitialized memory to an existing list. If the value of the buffer list is exposed to users, it may expose raw server side memory, potentially holding secrets, private data and code. This is a similar vulnerability to the infamousHeartbleed
flaw in OpenSSL.Proof of concept by ChALkeR
You can read more about the insecure
Buffer
behavior on our blog.Similar vulnerabilities were discovered in request, mongoose, ws and sequelize.
Remediation
Upgrade
tunnel-agent
to version 0.6.0 or higher.Note This is vulnerable only for Node <=4
References
The text was updated successfully, but these errors were encountered: