Tencent RapidJSON is vulnerable to privilege escalation due to an integer underflow 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 underflow vulnerability (when the file is parsed), leading to elevation of privilege.
CVE-2024-38517
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2024-37387 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 35EG Risk 35/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 31st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
July 9, 2024
Last Modified
April 15, 2026
Advisory Details (4)
Auto-updated Oct 11, 2026Security Update Guide - Microsoft Security Response Center
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38517commit 8269bc2bc289 (fmalita/rapidjson)
Fix landed in fmalita/rapidjson commit 8269bc2bc289 — awaiting tagged release
https://github.com/fmalita/rapidjson/commit/8269bc2bc289e9d343bae51cdf6d23ef0950e001Prevent int underflow when parsing exponents
Fix merged in Tencent/rapidjson PR #1261 on 2018-05-20 — awaiting tagged release
https://github.com/Tencent/rapidjson/pull/1261/commits/8269bc2bc289e9d343bae51cdf6d23ef0950e001Vendor Advisories for CVE-2024-38517(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | rapidjson-doc (1.1.0+dfsg2-3ubuntu0.1~esm1) @ bionic | 2026-10-28 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rapidjson | 1.1.0+dfsg2-7 ... 1.1.0+dfsg2-7.6 (6 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rapidjson | 1.1.0+dfsg2-7.1, 1.1.0+dfsg2-7.2, 1.1.0+dfsg2-7.3, 1.1.0+dfsg2-7.4, 1.1.0+dfsg2-7.6 |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rapidjson | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rapidjson | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 9× in last 7d / 39× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 96 of 236 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-28 05:55 UTCEG score recompute
- 2026-10-28 05:55 UTCVendor advisory
- 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-25 17:07 UTCEG score recompute
- 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-20 19:40 UTCEG score recompute
- 2026-10-20 19:40 UTCVendor advisory
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-18 07:10 UTCEG score recompute
- 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 71 moreShow fewer
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-12 17:50 UTCEG score recompute
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-11 21:15 UTCEG score recompute
- 2026-10-11 16:08 UTCEG score recompute
- 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-07 10:35 UTCOSV refresh
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-30 19:48 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-17 16:50 UTCOSV refresh
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-29 16:43 UTCOSV refresh
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-13 04:00 UTCOSV refresh
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2024-38517?
When was the CVE record for CVE-2024-38517 published?
Is CVE-2024-38517 actively exploited?
What is the CVSS score of CVE-2024-38517?
How do I remediate CVE-2024-38517?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-38517
Is Your Infrastructure Affected by CVE-2024-38517?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.