Bug 2531082 - CVE-2026-57161 pjproject: stack overflow handling Service-Route headers in a registration response [fedora-all]
Summary: CVE-2026-57161 pjproject: stack overflow handling Service-Route headers in a ...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: pjproject
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Jared Smith
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["09418bf5-eae8-4b71-ae97-a...
Depends On:
Blocks: CVE-2026-57161
TreeView+ depends on / blocked
 
Reported: 2026-09-09 17:25 UTC by Guilherme de Almeida Suckevicz
Modified: 2026-09-09 17:25 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2026-09-09 17:25:57 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

PJSIP is a free and open source multimedia communication library written in C. Prior to commit acc03b5, a stack buffer overflow exists in PJSUA when processing Service-Route headers in a registration response (update_service_route() in pjsua_acc.c). This affects applications that register using the PJSUA/PJSUA2 account API (the default registration path). The Service-Route URIs from a 2xx response to REGISTER are stored into a fixed-size array without bounding the number of headers; a registrar that returns an excessive number of Service-Route headers can write past the end of the array on the stack. The values written are internal pointers rather than arbitrary data, so the most likely impact is unexpected application termination (denial of service), though memory corruption cannot be excluded. The malicious response may come from a compromised or malicious registrar, or — over unprotected transports — a spoofed response. This issue has been patched via commit acc03b5.


Note You need to log in before you can comment on or make changes to this bug.