CVE-2008-4618
What it is
The Stream Control Transmission Protocol (sctp) implementation in the Linux kernel before 2.6.27 does not properly handle a protocol violation in which a parameter has an invalid length, which allows attackers to cause a denial of service (panic) via unspecified vectors, related to sctp_sf_violation_paramlen, sctp_sf_abort_violation, sctp_make_abort_violation, and incorrect data types in function calls.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 2.7% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.7% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 2.7% · EPSS, next 30 days
- Weakness
- CWE-20 · Improper input validation
- Record status
- Modified
Affected
- Linux Kernel ≤ 2.6.26.5
- Linux Kernel 2.2.27
- Linux Kernel 2.4.36
- Linux Kernel 2.4.36.1
- Linux Kernel 2.4.36.2
- Linux Kernel 2.4.36.3
- Linux Kernel 2.4.36.4
- Linux Kernel 2.4.36.5
Attack profile CVSS 2.0 · 7.8
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
Raw vector
AV:N/AC:L/Au:N/C:N/I:N/A:C
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2008-4618.md and follow it. Check whether this project is affected by CVE-2008-4618. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git%3Ba=commit%3Bh=ba0166708ef4da7eeb61dd92bbba4d5a749d6561
- http://lists.opensuse.org/opensuse-security-announce/2008-10/msg00010.html
- http://secunia.com/advisories/32918
- http://secunia.com/advisories/32998
- http://secunia.com/advisories/33586
- http://www.debian.org/security/2008/dsa-1681
- http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27
- http://www.openwall.com/lists/oss-security/2008/10/06/1
- http://www.redhat.com/support/errata/RHSA-2009-0009.html
- http://www.securityfocus.com/bid/31848
- http://www.ubuntu.com/usn/usn-679-1
- http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git%3Ba=commit%3Bh=ba0166708ef4da7eeb61dd92bbba4d5a749d6561
- http://lists.opensuse.org/opensuse-security-announce/2008-10/msg00010.html
- http://secunia.com/advisories/32918
- http://secunia.com/advisories/32998
- http://secunia.com/advisories/33586
- http://www.debian.org/security/2008/dsa-1681
- http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27
- http://www.openwall.com/lists/oss-security/2008/10/06/1
- http://www.redhat.com/support/errata/RHSA-2009-0009.html
- http://www.securityfocus.com/bid/31848
- http://www.ubuntu.com/usn/usn-679-1