Project Subscriptions
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 11 Sep 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Teluu
Teluu pjsip |
|
| CPEs | cpe:2.3:a:teluu:pjsip:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Teluu
Teluu pjsip |
|
| Metrics |
cvssV3_1
|
Wed, 09 Sep 2026 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 04 Sep 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pjsip
Pjsip pjproject |
|
| Vendors & Products |
Pjsip
Pjsip pjproject |
Fri, 04 Sep 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | PJSIP is a free and open source multimedia communication library written in C. Prior to commit d6a0e7f, a buffer overflow can occur in pjsip_generic_array_hdr_print() in pjsip/src/pjsip/sip_msg.c, the function that serializes generic array headers (such as Allow, Require, Supported, and Unsupported). Under certain output-buffer boundary conditions the function can write one byte past the end of the buffer. This is reachable mainly in applications that parse and re-serialize incoming SIP requests — for example a proxy, SBC, or B2BUA — where a remote peer can influence the serialized message. The out-of-bounds write is a single fixed byte; code execution and information disclosure are not demonstrated, and in typical pool-based allocations the byte falls within allocation slack. This issue has been patched via commit d6a0e7f. | |
| Title | PJSIP: SIP message header buffer overflow | |
| Weaknesses | CWE-193 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-08T17:33:34.357Z
Reserved: 2026-06-24T01:45:48.698Z
Link: CVE-2026-57160
Updated: 2026-09-08T16:50:28.639Z
Status : Analyzed
Published: 2026-09-04T18:17:53.740
Modified: 2026-09-11T15:31:44.923
Link: CVE-2026-57160
No data.
OpenCVE Enrichment
Updated: 2026-09-04T21:30:07Z