First published: Mon Aug 13 2012(Updated: )
The Update method in src/node_http_parser.cc in Node.js before 0.6.17 and 0.7 before 0.7.8 does not properly check the length of a string, which allows remote attackers to obtain sensitive information (request header contents) and possibly spoof HTTP headers via a zero length string.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Node.js | <=0.6.16 | |
Node.js | =0.7.0 | |
Node.js | =0.7.1 | |
Node.js | =0.7.2 | |
Node.js | =0.7.3 | |
Node.js | =0.7.4 | |
Node.js | =0.7.5 | |
Node.js | =0.7.6 | |
Node.js | =0.7.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-2330 is considered a moderate severity vulnerability due to its potential to expose sensitive information.
To fix CVE-2012-2330, upgrade Node.js to version 0.6.17 or higher, or to version 0.7.8 or higher.
CVE-2012-2330 allows remote attackers to obtain sensitive request header contents and potentially spoof HTTP headers.
CVE-2012-2330 affects Node.js versions before 0.6.17 and 0.7 versions before 0.7.8.
Yes, CVE-2012-2330 can lead to data leakage by allowing attackers to access sensitive information from request headers.