PfsenseApplication · Netgate
CVE-2015-1414
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 · uneditedInteger overflow in FreeBSD before 8.4 p24, 9.x before 9.3 p10. 10.0 before p18, and 10.1 before p6 allows remote attackers to cause a denial of service (crash) via a crafted IGMP packet, which triggers an incorrect size calculation and allocation of insufficient memory.
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 confidenceInteger overflow in FreeBSD's IGMP packet handling causes incorrect size calculation during memory allocation. When processing a specially crafted IGMP packet, the overflow results in allocating a buffer too small for the incoming data, leading to a crash when the system attempts to write beyond the allocated boundary.
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
PfsenseApplication
= 2.2.1
Debian LinuxOperating system
= 7.0
FreeBSDOperating system
= 8.4= 9.0= 9.1= 9.2= 9.3= 10.0= 10.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the operating system and versionRun 'uname -a' or 'cat /etc/os-release' for Linux, 'uname -a' for FreeBSD-based systems, or check the pfSense web GUI under System > Firmware > VersionAffected if The system is FreeBSD 8.4, 9.0, 9.1, 9.2, 9.3, 10.0, or 10.1; Debian 7.0; or pfSense 2.2.1
-
Determine if the system has received vendor patchesFor FreeBSD, run 'freebsd-version -u' to check the patch level, or check the kernel version with 'uname -v' against the patched versions (8.4p24+, 9.3p10+, 10.0p18+, 10.1p6+). For Debian, check the installed kernel with 'dpkg -l | grep kernel' and compare to fixed Debian 7.0 kernel packages.Affected if The system has not been patched to the vendor-supplied patch level for its FreeBSD version
-
Verify if IGMP or multicast routing is enabledFor FreeBSD-based systems, check if multicast routing is enabled by reviewing running services or kernel modules. On pfSense, check if IGMP proxy is configured under Services > IGMP Proxy. On Linux systems, check 'ip maddr' to see if multicast addresses are in use.Affected if IGMP processing is active on the system - the vulnerability triggers when specially crafted IGMP packets are processed
You are affected if you run an unpatched FreeBSD 8.4-10.1, Debian 7.0, or pfSense 2.2.1 with IGMP or multicast routing functionality enabled on a network segment that can receive unsolicited IGMP traffic.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-supplied patches for the affected FreeBSD versions (8.4 p24+, 9.3 p10+, 10.0 p18+, 10.1 p6+) or upgrade to supported stable releases. If immediate patching is not possible, consider network-level filtering of unexpected IGMP traffic at perimeter gateways.
Fix this in Pfsense
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-1414 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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