CVE-2014-7205
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 · uneditedEval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for the hapi server framework for Node.js allows remote attackers to execute arbitrary Javascript code via unspecified vectors.
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 confidenceThis is a critical remote code execution vulnerability in the bassmaster plugin for hapi. The internals.batch function in lib/batch.js uses eval() to process user-supplied input without proper sanitization, allowing attackers to inject and execute arbitrary JavaScript code on the server.
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< 1.5.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if bassmaster is installedCheck your project's package.json file for 'bassmaster' in the dependencies or devDependencies section, or run 'npm list bassmaster' to list installed packagesAffected if bassmaster is listed as a dependency
-
Check the bassmaster versionRun 'npm list bassmaster' or inspect the version in package.json to determine the exact version number installedAffected if The installed version is less than 1.5.2
-
Locate the vulnerable batch.js fileIn your node_modules directory, navigate to bassmaster/lib/batch.js and inspect the internals.batch function for eval() usageAffected if The file contains eval() being used to process user-supplied input in the batch function
-
Check if batch endpoint is exposedReview your hapi server configuration to see if the bassmaster plugin route (typically /batch) is registered and accessibleAffected if The batch endpoint is exposed and accepts user requests
You are affected if bassmaster is installed with a version prior to 1.5.2 and the batch endpoint is accessible, as this allows arbitrary code execution via unsanitized input to eval().
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.5.2
Update the bassmaster plugin to version 1.5.2 or later which removes the unsafe eval usage, and verify batch functionality continues to work correctly after the update.
1.5.2
- Check the current bassmaster version in your project by examining package.json or running 'npm list bassmaster'
- Upgrade bassmaster to version 1.5.2 or later by running 'npm install [email protected]' or 'npm update bassmaster'
- Verify the upgrade was successful by running 'npm list bassmaster' to confirm the installed version
- Test your application to ensure the batch functionality still works correctly after the upgrade
- Redeploy the updated application to all production environments
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7205 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-7205 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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