An out-of-bounds read and write flaw was found in the way SIPcrack 0.2 processed SIP traffic, because 0x00 termination of a payload array w…

published 2017-07-26 9y ago modified 2026-06-17 4mo ago also EUVD-2017-3266

cvss: 5.9; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.0%; EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits: 0; none known

An out-of-bounds read and write flaw was found in the way SIPcrack 0.2 processed SIP traffic, because 0x00 termination of a payload array was mishandled. A remote attacker could potentially use this flaw to crash the sipdump process by generating specially crafted SIP traffic.

Is CVE-2017-11654 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

Exploit prediction

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

Exploits and checks

openwall.com http://openwall.com/lists/oss-security/2017/07/26/1 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

CWE-125 Out-of-bounds Read
CWE-787 Out-of-bounds Write

References

openwall.com /lists/oss-security/2017/07/26/1
exploit, mailing-list, third-party-advisory
securityfocus.com /bid/100023
vdb-entry, broken-link, third-party-advisory

Sources

CVE List CVE-2017-11654
NVD CVE-2017-11654

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.