dbcve.org
JunosOperating system · Juniper

CVE-2007-6372

HIGH · 7.8 CVSS v2.0 Published 2007-12-15
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
Unspecified vulnerability in Juniper JUNOS 7.3 through 8.4 allows remote attackers to cause a denial of service (crash) via malformed BGP packets, possibly BGP UPDATE packets that trigger session flapping.

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 · moderate confidence

A denial of service vulnerability in Juniper JUNOS versions 7.3 through 8.4 allows remote attackers to crash the BGP routing process by sending malformed BGP UPDATE packets, causing session flapping and system crash.

MitigationUpgrade JUNOS to a version beyond 8.4 that contains the patch for this vulnerability; implement BGP route filtering and prefix validation as an interim mitigation.

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
JunosOperating system
Affected:= 7.3= 7.4= 7.5= 7.6= 8.0= 8.1= 8.2= 8.3= 8.4

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 installed JUNOS version
    Run 'show version' or 'show system information' from the CLI to obtain the exact JUNOS version number
    Affected if Version matches 7.3, 7.4, 7.5, 7.6, 8.0, 8.1, 8.2, 8.3, or 8.4
  2. Verify BGP protocol is configured
    Run 'show configuration protocols bgp' to see if BGP is configured and active
    Affected if BGP protocol is enabled and peer relationships exist in the configuration
  3. Confirm BGP is running
    Run 'show bgp summary' to check if BGP sessions are established and active
    Affected if Any BGP neighbors show as established or active
  4. Check for BGP peer exposure
    Review 'show configuration protocols bgp' output to identify external BGP (eGP) peers versus internal peers
    Affected if eBGP peers from untrusted networks are configured

You are affected if your Juniper device runs JUNOS versions 7.3 through 8.4 and has BGP protocol enabled and operational, exposing the device to malformed BGP UPDATE packets from peers.

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

Upgrade JUNOS to a version beyond 8.4 that contains the patch for this vulnerability; implement BGP route filtering and prefix validation as an interim mitigation.

Fix this in Junos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-6372 — 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-2007-6372 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