CVE-2024-36581
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 · uneditedA Prototype Pollution issue in abw badger-database 1.2.1 allows an attacker to execute arbitrary code via dist/badger-database.esm.
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 · moderate confidenceA Prototype Pollution vulnerability in abw badger-database version 1.2.1 allows attackers to modify JavaScript object prototypes via the dist/badger-database.esm file, potentially leading to arbitrary code execution. This is a high-severity (CVSS 7.6) vulnerability affecting a JavaScript library.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
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.
-
Locate badger-database in your project dependenciesSearch your package.json file or run 'npm list badger-database' or 'yarn list badger-database' to see if the library is listed as a dependencyAffected if The library is present in your node_modules or declared in package.json dependencies
-
Check the installed version of badger-databaseRun 'npm list badger-database' or check the version field in your package-lock.json or yarn.lock file for badger-databaseAffected if The version is exactly 1.2.1, as this is the vulnerable version specified in the CVE
-
Verify the vulnerable ESM file exists in your environmentCheck if the file dist/badger-database.esm exists in the badger-database package directory within node_modulesAffected if This file exists and is being loaded by your application, which is the attack vector for prototype pollution
-
Identify if user input is merged into objects using this libraryReview your codebase for calls to any badger-database functions that merge or assign data, and trace whether any user-controlled data reaches these functionsAffected if Untrusted or user-supplied input is being processed and merged into objects by badger-database methods, enabling prototype pollution attacks
You are affected if badger-database version 1.2.1 is installed and your application uses it to process untrusted input that gets merged into JavaScript objects.
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.
From vendor dataUpdate to a patched version of abw badger-database if available; otherwise, audit and sanitize all user input before merging into objects to prevent prototype pollution, and implement Object.freeze() on sensitive prototypes.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36581 — 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-2024-36581 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