CVE-2024-57708
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 · uneditedAn issue in OneTrust SDK v.6.33.0 allows a local attacker to cause a denial of service via the Object.setPrototypeOf, __proto__, and Object.assign components. NOTE: this is disputed by the Supplier who does not agree it is a prototype pollution vulnerability.
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 confidenceThe OneTrust SDK version 6.33.0 contains a vulnerability where local attackers can manipulate JavaScript object prototypes using Object.setPrototypeOf, __proto__, and Object.assign to cause denial of service. The supplier disputes whether this constitutes a prototype pollution vulnerability, but the mechanism allows manipulation of object inheritance that can lead to application instability or crash.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Identify OneTrust SDK versionSearch your codebase, dependency files (package.json, yarn.lock, package-lock.json), or bundled files for 'onetrust' or '@onetrust/sdk' and note the installed version numberAffected if The installed version is exactly 6.33.0
-
Locate OneTrust SDK integrationFind the main OneTrust SDK initialization file in your application and confirm it is version 6.33.0 by inspecting the imported module versionAffected if The SDK file confirms version 6.33.0
-
Search for Object.setPrototypeOf usageSearch your application code for calls to Object.setPrototypeOf where the prototype argument could be influenced by user input, query parameters, or API payloadsAffected if User-controllable data is passed to Object.setPrototypeOf without validation
-
Search for __proto__ property assignmentSearch your application code for assignments to __proto__ that use data from user requests, URLs, or external sourcesAffected if User input directly assigns to __proto__ properties
-
Search for Object.assign with untrusted dataSearch your application code for Object.assign calls where the source object contains data derived from user inputAffected if User-controllable data is passed as an argument to Object.assign
Your environment is affected if OneTrust SDK version 6.33.0 is deployed AND your application passes unvalidated user input into Object.setPrototypeOf, __proto__, or Object.assign operations.
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 dataImplement strict input validation and sanitization on all user-controllable data before using it in Object.setPrototypeOf, __proto__, or Object.assign operations. Consider upgrading to a patched version if available from OneTrust.
- 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-57708 — 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-57708 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