dbcve.org
FreeBSDOperating system

CVE-2014-8613

HIGH · 7.8 CVSS v2.0 Published 2015-02-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The sctp module in FreeBSD 10.1 before p5, 10.0 before p17, 9.3 before p9, and 8.4 before p23 allows remote attackers to cause a denial of service (NULL pointer dereference and kernel panic) via a crafted RE_CONFIG chunk.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Stream Control Transmission Protocol (sCTP) module in FreeBSD contains a NULL pointer dereference vulnerability when processing a specially crafted RE_CONFIG chunk. This flaw allows remote attackers to trigger a kernel panic, resulting in a denial of service condition.

MitigationApply the appropriate FreeBSD security patches (p5 for 10.1, p17 for 10.0, p9 for 9.3, p23 for 8.4) to address the NULL pointer dereference in the sctp module, and consider filtering or rate-limiting SCTP traffic at network borders if immediate patching is not feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreeBSDOperating system
Affected:= 8.4= 9.3= 10.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FreeBSD version
    Run 'uname -r' or check /etc/os-release (if present) to determine the installed FreeBSD version
    Affected if Version matches 8.4, 9.3, or 10.1 exactly
  2. Verify SCTP module is loaded
    Run 'kldstat | grep sctp' to check if the SCTP kernel module is currently loaded
    Affected if The sctp module appears in the loaded module list (sctp syscalls, sctp_core, etc.)
  3. Check SCTP boot configuration
    Inspect /boot/loader.conf for lines containing 'sctp_load="YES"' or check /etc/rc.conf for 'sctp_enable="YES"'
    Affected if SCTP is configured to load at boot or is currently enabled on the system
  4. Verify SCTP network usage
    Run 'netstat -s -p sctp' or check if any SCTP associations exist via 'sctp_status' (if installed)
    Affected if The system is actively processing SCTP traffic or has SCTP endpoints configured

A system is affected only if it runs FreeBSD 8.4, 9.3, or 10.1 AND has the SCTP module loaded or enabled, as the vulnerability is triggered by specially crafted SCTP RE_CONFIG chunks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate FreeBSD security patches (p5 for 10.1, p17 for 10.0, p9 for 9.3, p23 for 8.4) to address the NULL pointer dereference in the sctp module, and consider filtering or rate-limiting SCTP traffic at network borders if immediate patching is not feasible.

Fix this in FreeBSD Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-8613 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data