CVE-2015-7748
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 · uneditedJuniper chassis with Trio (Trinity) chipset line cards and Junos OS 13.3 before 13.3R8, 14.1 before 14.1R6, 14.2 before 14.2R5, and 15.1 before 15.1R2 allow remote attackers to cause a denial of service (MPC line card crash) via a crafted uBFD packet.
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 confidenceA denial of service vulnerability in Juniper Junos OS on Trio (Trinity) chipset line cards allows remote attackers to crash MPC line cards by sending specially crafted uBFD (Bidirectional Forwarding Detection) packets. The vulnerability affects multiple Junos OS version branches before their respective R6/R5/R2 releases.
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= 13.3= 14.1= 14.2= 15.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
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 Junos OS versionExecute 'show version' on the device CLI to retrieve the installed Junos OS release versionAffected if The version shows 13.3, 14.1, 14.2, or 15.1 (any build before their respective R8/R6/R5/R2 updates)
-
Confirm the fixed version has not been appliedCompare the installed version against the patched releases: 13.3R8, 14.1R6, 14.2R5, or 15.1R2. Check if the installed version predates these releasesAffected if The device runs any version earlier than the fixed releases listed above within the 13.3, 14.1, 14.2, or 15.1 branches
-
Identify Trio (Trinity) chipset MPC line cardsExecute 'show chassis hardware' or 'show hardware' to list installed MPC (Modular PIC Concentrator) line cards and check if they are Trio-based modelsAffected if The device contains Trio/Trinity chipset MPC line cards (the vulnerability only affects Trio-based line cards)
-
Check if uBFD protocol is enabledRun 'show configuration protocols bfd' or 'show configuration | match ubfd' to see if Bidirectional Forwarding Detection is configuredAffected if uBFD is actively configured on the device; the device is vulnerable only when uBFD is running and receives the crafted packets
A device is affected if it runs Junos OS versions 13.3, 14.1, 14.2, or 15.1 before their respective security updates, has Trio chipset MPC line cards, and has uBFD protocol enabled, allowing remote attackers to crash the MPC line cards via crafted packets.
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 appropriate Junos OS update (13.3R8, 14.1R6, 14.2R5, or 15.1R2 or later) to affected devices. Consider filtering uBFD traffic at network boundaries as a temporary mitigation if immediate patching is not feasible.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7748 — 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-7748 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