CVE-2017-11654: An out-of-bounds read and write flaw was found in the way SIPcrack 0.2 processed SIP traffic, because 0x00 ter
CVE-2017-11654 is a medium-severity flaw (CVSS 5.9) affecting sipcrack. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-11654?
sipcrack: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2017-11654 being exploited?
CVE-2017-11654 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2017-11654 affect?
CVE-2017-11654 affects sipcrack. Severity is medium (CVSS 5.9). 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 gene
How urgent is CVE-2017-11654?
Priority 51/100. Public exploit reference; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2017-11655 HIGH 7.5 DOWNGRADE A memory leak was found in the way SIPcrack 0.2 handled processing of SIP traffic, because a lines array was m