CWE
252 476
Advisory Published
Updated

CVE-2024-42491: A malformed Contact or Record-Route URI in an incoming SIP request can cause Asterisk to crash when res_resolver_unbound is used

First published: Thu Sep 05 2024(Updated: )

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.

Credit: security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Asterisk<18.24.3<20.9.3<21.4.3
Asterisk Certified Asterisk<18.9-cert12<20.7-cert2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-42491?

    The severity of CVE-2024-42491 is classified as moderate, posing potential risks for Asterisk installations that utilize specific SIP request formats.

  • How do I fix CVE-2024-42491?

    To mitigate CVE-2024-42491, upgrade your Asterisk to versions 18.24.3, 20.9.3, or 21.4.3, or for certified Asterisk, update to versions 18.9-cert12 or 20.7-cert2.

  • What versions of Asterisk are affected by CVE-2024-42491?

    CVE-2024-42491 affects Asterisk versions prior to 18.24.3, 20.9.3, and 21.4.3, as well as certified-asterisk versions before 18.9-cert12 and 20.7-cert2.

  • What consequence does CVE-2024-42491 pose for users?

    CVE-2024-42491 may lead to unexpected behavior when Asterisk processes SIP requests directed at certain URI formats.

  • Is there a workaround for CVE-2024-42491?

    There are no documented workarounds for CVE-2024-42491; updating to a patched version is the recommended solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203