CVE-2024-34730

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-01-22. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In multiple locations, there is a possible bypass of user consent to enabling new Bluetooth HIDs due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

January 21, 2025

Last Modified

April 22, 2025

References (1)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 17× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-26 14:53 UTCEPSS rescore
  2. 2026-07-25 14:16 UTCEPSS rescore
  3. 2026-07-24 14:16 UTCEPSS rescore
  4. 2026-07-23 02:37 UTCEG score recompute
  5. 2026-07-18 10:03 UTCEPSS rescore
  6. 2026-07-16 17:02 UTCEPSS rescore
  7. 2026-07-13 22:29 UTCEPSS rescore
  8. 2026-07-13 06:11 UTCEPSS rescore
  9. 2026-07-08 15:14 UTCEPSS rescore
  10. 2026-07-08 15:13 UTCEPSS rescore
  11. 2026-07-07 13:45 UTCEPSS rescore
  12. 2026-07-06 16:26 UTCEPSS rescore
  13. 2026-07-05 02:29 UTCEPSS rescore
  14. 2026-06-28 14:06 UTCEPSS rescore
  15. 2026-06-28 14:06 UTCEPSS rescore
  16. 2026-06-28 04:55 UTCEPSS rescore
  17. 2026-06-28 04:55 UTCEPSS rescore
  18. 2026-06-23 21:32 UTCEPSS rescore
  19. 2026-06-23 21:32 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-21 01:58 UTCEPSS rescore
  22. 2026-06-19 19:25 UTCEPSS rescore
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-17 17:52 UTCEPSS rescore
  25. 2026-06-15 17:47 UTCEPSS rescore
Show 22 more
  1. 2026-06-14 23:16 UTCEPSS rescore
  2. 2026-06-12 23:11 UTCEPSS rescore
  3. 2026-06-10 22:17 UTCEPSS rescore
  4. 2026-06-08 14:16 UTCEPSS rescore
  5. 2026-06-07 15:24 UTCEPSS rescore
  6. 2026-06-07 15:24 UTCEPSS rescore
  7. 2026-06-06 13:46 UTCEPSS rescore
  8. 2026-06-06 13:46 UTCEPSS rescore
  9. 2026-06-05 22:46 UTCEPSS rescore
  10. 2026-06-05 22:46 UTCEPSS rescore
  11. 2026-06-05 06:09 UTCEPSS rescore
  12. 2026-06-05 06:09 UTCEPSS rescore
  13. 2026-06-02 20:12 UTCEPSS rescore
  14. 2026-06-01 13:51 UTCEPSS rescore
  15. 2026-06-01 13:51 UTCEPSS rescore
  16. 2026-05-31 22:30 UTCEPSS rescore
  17. 2026-05-31 22:30 UTCEPSS rescore
  18. 2026-05-31 00:15 UTCEPSS rescore
  19. 2026-05-31 00:15 UTCEPSS rescore
  20. 2026-05-30 12:54 UTCEG score recompute
  21. 2026-05-30 12:54 UTCGHSA enrichment
  22. 2026-05-29 13:43 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-34730?
CVE-2024-34730 is a high vulnerability published on January 21, 2025. In multiple locations, there is a possible bypass of user consent to enabling new Bluetooth HIDs due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2024-34730 disclosed?
CVE-2024-34730 was first published in the National Vulnerability Database on January 21, 2025, with the most recent update on April 22, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-34730 actively exploited?
CVE-2024-34730 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.8% of all scored CVEs.
What is the CVSS score of CVE-2024-34730?
CVE-2024-34730 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-34730?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-34730, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-34730

Explore →

Is Your Infrastructure Affected by CVE-2024-34730?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs