CVE-2024-53845

MEDIUMNVD 6.66.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.6 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.6Exploit: NoneExposed: 0

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

ESPTouch is a connection protocol for internet of things devices. In the ESPTouchV2 protocol, while there is an option to use a custom AES key, there is no option to set the IV (Initialization Vector) prior to versions 5.3.2, 5.2.4, 5.1.6, and 5.0.8. The IV is set to zero and remains constant throughout the product's lifetime. In AES/CBC mode, if the IV is not properly initialized, the encrypted output becomes deterministic, leading to potential data leakage. To address the aforementioned issues, the application generates a random IV when activating the AES key starting in versions 5.3.2, 5.2.4, 5.1.6, and 5.0.8. This IV is then transmitted along with the provision data to the provision device. The provision device has also been equipped with a parser for the AES IV. The upgrade is applicable for all applications and users of ESPTouch v2 component from ESP-IDF. As it is implemented in the ESP Wi-Fi stack, there is no workaround for the user to fix the application layer without upgrading the underlying firmware.

CVSS v3
6.6
EG Score
6.6(medium)
EPSS
43.8%
KEV
Not listed

Published

December 12, 2024

Last Modified

April 15, 2026

References (9)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 43× 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.

Showing the most recent 100 of 116 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-53845?
CVE-2024-53845 is a medium vulnerability published on December 12, 2024. ESPTouch is a connection protocol for internet of things devices. In the ESPTouchV2 protocol, while there is an option to use a custom AES key, there is no option to set the IV (Initialization Vector) prior to versions 5.3.2, 5.2.4, 5.1.6, and 5.0.8. The IV is set to zero and remains constant…
When was CVE-2024-53845 disclosed?
CVE-2024-53845 was first published in the National Vulnerability Database on December 12, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-53845 actively exploited?
CVE-2024-53845 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 43.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-53845?
CVE-2024-53845 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2024-53845?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-53845, 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-53845

Explore →

Is Your Infrastructure Affected by CVE-2024-53845?

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

Start Free Scan →Browse All CVEs