Skip to content
Fencer Intel
medium 4.6

CVE-2014-8612 json

Multiple array index errors in the Stream Control Transmission Protocol (SCTP) module in FreeBSD 10.1 before p5, 10.0 before p17, 9.3 befor…

published 11y ago modified 4mo ago also EUVD-2014-8449

cvss
4.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
1
Exploit-DB

Summary

Multiple array index errors in the Stream Control Transmission Protocol (SCTP) module in FreeBSD 10.1 before p5, 10.0 before p17, 9.3 before p9, and 8.4 before p23 allow local users to (1) gain privileges via the stream id to the setsockopt function, when setting the SCTIP_SS_VALUE option, or (2) read arbitrary kernel memory via the stream id to the getsockopt function, when getting the SCTP_SS_PRIORITY option.

Is CVE-2014-8612 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

Timeline

  1. First public exploit (EDB-35938)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-35938 FreeBSD - Multiple Vulnerabilities dos, 2015-01-29
  • seclists.org http://seclists.org/fulldisclosure/2015/Jan/107 referenced PoC, tagged "exploit" by a source, unverified
  • coresecurity.com http://www.coresecurity.com/advisories/freebsd-kernel-multiple-vulnerabilities referenced PoC, tagged "exploit" by a source, unverified
  • securitytracker.com http://www.securitytracker.com/id/1031648 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

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.