CVE-2024-39684
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 · uneditedTencent RapidJSON is vulnerable to privilege escalation due to an integer overflow in the `GenericReader::ParseNumber()` function of `include/rapidjson/reader.h` when parsing JSON text from a stream. An attacker needs to send the victim a crafted file which needs to be opened; this triggers the integer overflow vulnerability (when the file is parsed), leading to elevation of privilege.
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 confidenceTencent RapidJSON contains an integer overflow vulnerability in the GenericReader::ParseNumber() function in include/rapidjson/reader.h. When parsing a crafted JSON file from a stream, the integer overflow can be triggered, potentially leading to privilege escalation. The attack requires user interaction (opening a malicious file).
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 RapidJSON installationSearch for rapidjson/reader.h header file or librapidjson in your project dependencies, package manager listings, or installed librariesAffected if RapidJSON library is present in the environment
-
Identify RapidJSON versionCheck the version string in the reader.h header file (look for version defines like RAPIDJSON_VERSION), or check your dependency manifest/package lock file for the rapidjson versionAffected if The installed version is prior to the patched version (any version prior to the fix for CVE-2024-39684)
-
Determine if JSON stream parsing is usedSearch source code for usage of GenericReader, Reader, or IStreamWrapper classes being used to parse JSON from file streams or network inputAffected if The application uses GenericReader or Reader to parse JSON from streams/files
-
Check for untrusted input handlingReview if the JSON parsing code processes input from user-uploaded files, network sources, or other untrusted origins without prior validationAffected if The application parses JSON from untrusted or user-supplied sources
-
Verify user interaction modelIdentify if the parsing is triggered by user actions such as opening files, clicking links, or providing input that flows to the JSON parserAffected if JSON parsing is triggered by user interaction with untrusted files or input
A user is affected if RapidJSON is used to parse untrusted JSON from streams/files and the version is unpatched.
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 Tencent RapidJSON to the latest version that addresses this vulnerability. If no patch is available, implement strict file validation before parsing and consider sandboxing file parsing operations to limit impact of potential exploitation.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39684 — 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-39684 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