CVE-2026-90780

7.5

SIPp · sipp

SIPp through 3.7.7 contains a buffer overflow vulnerability in the get_header() function that allows unauthenticated remote attackers to crash the process via crafted SIP messages.

Executive summary

A heap-based buffer overflow vulnerability in SIPp allows unauthenticated remote attackers to cause a denial of service by sending specifically crafted SIP packets.

Vulnerability

The vulnerability resides in the get_header() function within src/sip_parser.cpp, where the application fails to properly validate the size of incoming SIP header content. An unauthenticated remote attacker can supply header content exceeding 20,490 bytes, triggering a buffer overflow that crashes the application process.

Business impact

Successful exploitation of this vulnerability results in a denial of service for the affected SIPp instance. Given that SIPp is frequently used for performance testing and stress testing of telecommunications infrastructure, an unexpected process crash can lead to significant testing downtime, loss of test data, and potential disruption to workflows reliant on the availability of the SIPp tool. The CVSS score of 7.5 reflects the high impact on availability, even though the vulnerability does not currently facilitate remote code execution or data theft.

Remediation

Immediate Action: Organizations should restrict network access to SIPp instances to trusted administrative networks and monitor for potential vendor patches to address the overflow in the get_header() function.

Proactive Monitoring: Security teams should monitor system logs and process status for unexpected terminations or segmentation faults in the sipp executable.

Compensating Controls: Deploy a network-level firewall or session border controller to inspect and drop malformed or oversized SIP packets before they reach the SIPp instance.

Exploitation status

Public Exploit Available: No

Analyst recommendation

The vulnerability presents a clear risk to service availability for those utilizing SIPp in exposed environments. While no patch is currently identified, administrators must prioritize network segmentation and packet filtering to prevent unauthorized actors from reaching the vulnerable parsing logic. Once a vendor update becomes available, it should be applied as part of the standard patch management cycle to fully remediate the underlying buffer handling flaw.

More SIPp CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by Tristan Madani, per the CVE Program record.