CVE-2024-29640

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 1.2% (66th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Elevated
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

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

An issue in aliyundrive-webdav v.2.3.3 and before allows a remote attacker to execute arbitrary code via a crafted payload to the sid parameter in the action_query_qrcode component.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
1.2%
EPSS %ILE
66th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

March 29, 2024

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Oct 11, 2026
No fix on record yet.
Web page

GitHub - messense/aliyundrive-webdav: 阿里云盘 WebDAV 服务 · GitHub

https://github.com/messense/aliyundrive-webdav
Web page

vuln/detail.md at main · lakemoon602/vuln · GitHub

https://github.com/lakemoon602/vuln/blob/main/detail.md

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipaliyundrive-webdav—ghsa
rustaliyundrive-webdav—ghsa

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

(2 across 2 ecosystems)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
aliyundrive-webdav—
  • every version through 2.3.3: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
aliyundrive-webdav0.1.0 ... 2.3.3 (108 versions)
  • every version through 2.3.3: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 29× 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 87 of 195 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. 13 repeat rows among the latest 100 are merged into the row they repeat. The 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 21:21 UTCEG score recompute
  2. 2026-10-11 16:15 UTCEG score recompute
  3. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  4. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  5. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  6. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  7. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  8. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  9. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  10. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  11. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  12. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  13. 2026-09-30 19:41 UTCEG score recompute
  14. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  15. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  16. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  17. 2026-09-27 13:43 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  18. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  19. 2026-09-26 00:23 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  20. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  21. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  22. 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  23. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  24. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  25. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.2% · 66th percentile
Show 62 more
  1. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  2. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  3. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  4. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  5. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  6. 2026-09-11 09:35 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  7. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  8. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  9. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  10. 2026-09-05 15:26 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  11. 2026-09-04 13:58 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  12. 2026-09-04 05:05 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  13. 2026-09-02 14:10 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  14. 2026-09-01 13:52 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  15. 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  16. 2026-08-30 01:20 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  17. 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  18. 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  19. 2026-08-26 14:44 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  20. 2026-08-25 13:47 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  21. 2026-08-24 14:15 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  22. 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  23. 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  24. 2026-08-20 22:53 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  25. 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  26. 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  27. 2026-08-17 13:45 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  28. 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  29. 2026-08-16 02:13 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  30. 2026-08-15 01:28 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  31. 2026-08-13 21:59 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  32. 2026-08-12 13:49 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  33. 2026-08-11 13:40 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  34. 2026-08-10 23:58 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  35. 2026-08-09 13:45 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  36. 2026-08-08 16:35 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  37. 2026-08-07 16:25 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  38. 2026-08-06 13:45 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  39. 2026-08-05 19:16 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  40. 2026-08-04 15:08 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  41. 2026-08-04 10:36 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  42. 2026-08-03 10:34 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  43. 2026-08-02 02:25 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  44. 2026-08-01 04:14 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  45. 2026-07-30 16:26 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  46. 2026-07-30 01:29 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  47. 2026-07-28 15:34 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  48. 2026-07-27 14:11 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  49. 2026-07-26 14:53 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  50. 2026-07-25 14:16 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  51. 2026-07-24 14:16 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  52. 2026-07-23 14:17 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  53. 2026-07-23 02:35 UTCEG score recompute
  54. 2026-07-22 14:07 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  55. 2026-07-21 15:23 UTCEPSS rescoreEPSS 1.2% · 63rd percentile
  56. 2026-07-20 17:06 UTCEPSS rescoreEPSS 1.2% · 63rd percentile
  57. 2026-07-19 14:30 UTCEPSS rescoreEPSS 1.2% · 63rd percentile
  58. 2026-07-19 02:28 UTCEPSS rescoreEPSS 1.2% · 63rd percentile
  59. 2026-07-18 10:03 UTCEPSS rescoreEPSS 1.2% · 63rd percentile
  60. 2026-07-16 17:01 UTCEPSS rescoreEPSS 1.2% · 63rd percentile
  61. 2026-07-15 16:56 UTCEPSS rescoreEPSS 1.2% · 63rd percentile
  62. 2026-07-15 01:59 UTCEPSS rescoreEPSS 1.2% · 63rd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-29640?
CVE-2024-29640 is a critical-severity vulnerability; its CVE record was published on March 29, 2024. An issue in aliyundrive-webdav v.2.3.3 and before allows a remote attacker to execute arbitrary code via a crafted payload to the sid parameter in the actionqueryqrcode component.
When was the CVE record for CVE-2024-29640 published?
The CVE record for CVE-2024-29640 was published on March 29, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 9, 2026; the record at its source may have been updated since.
Is CVE-2024-29640 actively exploited?
CVE-2024-29640 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-29640?
CVE-2024-29640 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2024-29640?
No fix for CVE-2024-29640 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-29640

Explore →

Is Your Infrastructure Affected by CVE-2024-29640?

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

Book a Demo →Browse All CVEs