dbcve.org
Node.jsApplication · Joyent

CVE-2014-7192

HIGH · 10.0 CVSS v2.0 Published 2014-12-11
Fix available
A fix is available. Upgrade to after 0.10.32 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Eval injection vulnerability in index.js in the syntax-error package before 1.1.1 for Node.js 0.10.x, as used in IBM Rational Application Developer and other products, allows remote attackers to execute arbitrary code via a crafted file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Eval injection vulnerability in the syntax-error npm package's index.js allows remote attackers to execute arbitrary code by supplying a crafted file. The vulnerability exists in versions before 1.1.1 when used with Node.js 0.10.x, and affects any application that processes untrusted JavaScript files through this library.

MitigationUpgrade syntax-error package to version 1.1.1 or later. If direct upgrade is not possible, implement strict file validation and avoid using eval() on untrusted input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Node.jsApplication
Affected:<= 0.10.32

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if syntax-error package is installed
    Run 'npm list syntax-error' in the project directory, or check for 'syntax-error' in package.json dependencies
    Affected if syntax-error appears in the dependency tree
  2. Check installed version of syntax-error
    Run 'npm list syntax-error' to see the installed version, or check node_modules/syntax-error/package.json for the version field
    Affected if version is below 1.1.1 (e.g., 1.1.0, 1.0.0, or any version before 1.1.1)
  3. Check Node.js version in use
    Run 'node --version' to determine the Node.js runtime version
    Affected if Node.js version is 0.10.x and specifically <= 0.10.32
  4. Determine if untrusted JavaScript files are processed
    Review application code for calls to syntax-error functions (e.g., syntaxError(file)) that process files from untrusted sources such as user uploads, external APIs, or dynamic content
    Affected if The application uses syntax-error to parse or validate JavaScript from untrusted sources without additional validation

The environment is affected if syntax-error version below 1.1.1 is installed, Node.js 0.10.x (<=0.10.32) is in use, AND the application processes untrusted JavaScript files through this library.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.10.32
Vendor patch github.com →
Interim mitigation

Upgrade syntax-error package to version 1.1.1 or later. If direct upgrade is not possible, implement strict file validation and avoid using eval() on untrusted input.

Recommended fix High confidence

[email protected] or later (for Node.js 0.10.x environments)

  1. Identify all projects or dependencies that include the syntax-error package (e.g., by running `npm ls syntax-error` or checking package.json files)
  2. Update the syntax-error package to version 1.1.1 or later by running `npm install syntax-error@latest` or by updating the version in package.json and running `npm install`
  3. Verify the installed version is 1.1.1 or higher using `npm list syntax-error`
  4. Rebuild or restart any services that use this package to ensure the updated code is loaded
  5. Test the application to confirm functionality remains intact after the upgrade
Caveat Minimal risk - this is a patch release containing security fixes; however, test thoroughly as with any dependency update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Node.js Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-7192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-7192 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data