CVE-2025-47779: Using malformed From header can forge identity with ";" or NULL in name portion
Asterisk is an open-source private branch exchange (PBX). Prior to versions 18.26.2, 20.14.1, 21.9.1, and 22.4.1 of Asterisk and versions 18.9-cert14 and 20.7-cert5 of certified-asterisk, SIP requests of the type MESSAGE (RFC 3428) authentication do not get proper alignment. An authenticated attacker can spoof any user identity to send spam messages to the user with their authorization token. Abuse of this security issue allows authenticated attackers to send fake chat messages can be spoofed to appear to come from trusted entities. Even administrators who follow Security best practices and Security Considerations can be impacted. Therefore, abuse can lead to spam and enable social engineering, phishing and similar attacks. Versions 18.26.2, 20.14.1, 21.9.1, and 22.4.1 of Asterisk and versions 18.9-cert14 and 20.7-cert5 of certified-asterisk fix the issue.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-47779?
CVE-2025-47779 is classified as a high severity vulnerability due to improper authentication handling.
How do I fix CVE-2025-47779?
To mitigate CVE-2025-47779, upgrade Asterisk to versions 18.26.2, 20.14.1, 21.9.1, 22.4.1, or the respective certified-asterisk versions.
What versions of Asterisk are affected by CVE-2025-47779?
CVE-2025-47779 affects Asterisk versions prior to 18.26.2, 20.14.1, 21.9.1, and 22.4.1, as well as certified-asterisk versions prior to 18.9-cert14 and 20.7-cert5.
What type of requests does CVE-2025-47779 impact?
CVE-2025-47779 specifically impacts SIP MESSAGE requests as defined by RFC 3428.
What is the main issue with CVE-2025-47779?
The main issue with CVE-2025-47779 is that it involves improper alignment during the authentication process for SIP MESSAGE requests.