Skip to content
Fencer Intel
high 7.7

CVE-2025-47779 json

Using malformed From header can forge identity with ";" or NULL in name portion

published last yr. modified 4mo ago also EUVD-2025-16166

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

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.

Patch / fix

  • asterisk certified_asterisk 18.9-cert14, 18.26.2, 20.7-cert5, 20.14.1, 21.9.1, 22.4.1
  • asterisk open_source 18.9-cert14, 18.26.2, 20.7-cert5, 20.14.1, 21.9.1, 22.4.1
  • digium asterisk 18.9-cert14, 18.26.2, 20.7-cert5, 20.14.1, 21.9.1, 22.4.1
  • digium certified_asterisk 18.9-cert14, 18.26.2, 20.7-cert5, 20.14.1, 21.9.1, 22.4.1
  • sangoma certified_asterisk 18.9-cert14, 18.26.2, 20.7-cert5, 20.14.1, 21.9.1, 22.4.1
  • asterisk Debian 14 1:22.4.1~dfsg+~cs6.15.60671435-1

debian advisories DEBIAN-CVE-2025-47779

Is CVE-2025-47779 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-47779 updated cvss 6.5

asterisk: Using malformed From header can forge identity with ";" or NULL in name portion

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/asterisk/asterisk/security/advisories/GHSA-2grh-7mhv-fcfw referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected products

  • asterisk asterisk

Classification

Weakness
  • CWE-140 Improper Neutralization of Delimiters
  • CWE-792 Incomplete Filtering of One or More Instances of Special Elements

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.