CVE-2024-36575
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 getsetprop 1.1.0 allows an attacker to execute arbitrary code via global.accessor.
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 confidenceThis is a Prototype Pollution vulnerability in the getsetprop JavaScript library version 1.1.0. The vulnerability allows attackers to modify the prototype of JavaScript objects through the global.accessor function, potentially leading to arbitrary code execution. Prototype pollution attacks exploit the way JavaScript handles object prototypes, allowing injection of malicious properties into existing objects.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 getsetprop in dependenciesSearch your project for package.json files and inspect the dependencies or devDependencies sections, or check node_modules for a getsetprop directoryAffected if getsetprop appears in your dependencies or node_modules folder
-
Identify installed versionOpen node_modules/getsetprop/package.json and read the version field, or check your lock file (package-lock.json or yarn.lock) for the getsetprop version entryAffected if the installed version is 1.1.0
-
Find usage of global.accessorSearch your codebase for patterns such as global.accessor, require('getsetprop'), or import statements that bring in getsetprop functionalityAffected if your code invokes the global.accessor function from this library
-
Audit input to accessor functionTrace the data flow from user-supplied input (request parameters, headers, file contents, or environment variables) to any calls of the accessor function and verify whether input is validated or sanitized before reaching itAffected if untrusted or user-controlled input can reach the global.accessor call without proper validation
Your environment is affected if getsetprop version 1.1.0 is present in your project and untrusted input can flow into the global.accessor function without sanitization.
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 dataUpgrade to a patched version of getsetprop if available; otherwise, remove or replace the library. Audit the codebase for all usage of the vulnerable library and ensure no untrusted input can reach the affected function.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36575 — 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-36575 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