CVE-2024-42491

MEDIUMNVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 57% 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
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.7Exploit: None knownExposed: 0

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

Asterisk is an open-source private branch exchange (PBX). Prior to versions 18.24.3, 20.9.3, and 21.4.3 of Asterisk and versions 18.9-cert12 and 20.7-cert2 of certified-asterisk, if Asterisk attempts to send a SIP request to a URI whose host portion starts with .1 or [.1], and res_resolver_unbound is loaded, Asterisk will crash with a SEGV. To receive a patch, users should upgrade to one of the following versions: 18.24.3, 20.9.3, 21.4.3, certified-18.9-cert12, certified-20.7-cert2. Two workarounds are available. Disable res_resolver_unbound by setting noload = res_resolver_unbound.so in modules.conf, or set rewrite_contact = yes on all PJSIP endpoints. NOTE: This may not be appropriate for all Asterisk configurations.

CVSS v3
5.7
EG Score
5.7(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity57% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

September 5, 2024

Last Modified

November 3, 2025

References (7)

Affected Packages

(10 across 10 ecosystems)
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
asterisk—18.24.3-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
asterisk—18.24.3-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
asterisk—20.9.3-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
asterisk—20.9.3-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
asterisk—20.9.3-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
asterisk—20.9.3-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
asterisk—20.9.3-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
asterisk—20.9.3-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
asterisk1:16.16.1~dfsg+~2.10-1 ... 1:16.28.0~dfsg-0+deb11u4 (16 versions)1:16.28.0~dfsg-0+deb11u5—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
asterisk0.1.11-3 ... 1:20.8.1~dfsg+~cs6.14.40431414-1 (273 versions)1:20.9.3~dfsg+~cs6.14.60671435-1—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 28× 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 159 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-42491?
CVE-2024-42491 is a medium vulnerability published on September 5, 2024. Asterisk is an open-source private branch exchange (PBX). Prior to versions 18.24.3, 20.9.3, and 21.4.3 of Asterisk and versions 18.9-cert12 and 20.7-cert2 of certified-asterisk, if Asterisk attempts to send a SIP request to a URI whose host portion starts with .1 or [.1], and resresolverunbound is…
When was CVE-2024-42491 disclosed?
CVE-2024-42491 was first published in the National Vulnerability Database on September 5, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-42491 actively exploited?
CVE-2024-42491 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.3% of all scored CVEs.
What is the CVSS score of CVE-2024-42491?
CVE-2024-42491 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2024-42491?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-42491, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2024-42491?

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

Start Free Scan →Browse All CVEs