YJSoft/macos-plist

CVE-2014-10064 (High) detected in qs-0.6.6.tgz, qs-0.6.5.tgz - autoclosed

Closed this issue · 1 comments

CVE-2014-10064 - High Severity Vulnerability

Vulnerable Libraries - qs-0.6.6.tgz, qs-0.6.5.tgz

qs-0.6.6.tgz

querystring parser

Library home page: https://registry.npmjs.org/qs/-/qs-0.6.6.tgz

Path to dependency file: macos-plist/package.json

Path to vulnerable library: macos-plist/node_modules/qs/package.json

Dependency Hierarchy:

  • zuul-3.12.0.tgz (Root Library)
    • express-3.4.8.tgz
      • connect-2.12.0.tgz
        • qs-0.6.6.tgz (Vulnerable Library)
qs-0.6.5.tgz

querystring parser

Library home page: https://registry.npmjs.org/qs/-/qs-0.6.5.tgz

Path to dependency file: macos-plist/package.json

Path to vulnerable library: macos-plist/node_modules/superagent/node_modules/qs/package.json

Dependency Hierarchy:

  • zuul-3.12.0.tgz (Root Library)
    • superagent-0.15.7.tgz
      • qs-0.6.5.tgz (Vulnerable Library)

Found in HEAD commit: 9cee3646cabeaba7e6010d3ec4163529bcec875d

Found in base branch: master

Vulnerability Details

The qs module before 1.0.0 does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time. An attacker could leverage this to cause a temporary denial-of-service condition, for example, in a web application, other requests would not be processed while this blocking is occurring.

Publish Date: 2018-05-31

URL: CVE-2014-10064

CVSS 3 Score Details (7.5)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • Integrity Impact: None
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://nodesecurity.io/advisories/28

Release Date: 2014-08-06

Fix Resolution: Update to version 1.0.0 or later


Step up your Open Source Security Game with WhiteSource here

✔️ This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.