CVE-2013-6958
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 NetScreen Firewall running ScreenOS 5.4, 6.2, or 6.3, when the Ping of Death screen is disabled, allows remote attackers to cause a denial of service via a crafted 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 remote denial of service vulnerability exists in Juniper NetScreen firewalls running ScreenOS versions 5.4, 6.2, and 6.3. When the Ping of Death screen protection is disabled, an attacker can send a specially crafted packet to cause the device to crash or become unresponsive.
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= 5.4.0= 6.2.0= 6.3.0all versionsall versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/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 NetScreen device modelUse the device's CLI command to display hardware and system information (for example, 'get chassis' or 'show system information') to determine if the device is a NetScreen 5200 or NetScreen 5400Affected if The device model is NetScreen 5200 or NetScreen 5400 (all versions of these models are affected)
-
Check the ScreenOS versionUse the CLI command to display the ScreenOS version (for example, 'get system' or 'show version') and compare it to the affected versions 5.4.x, 6.2.x, and 6.3.xAffected if The installed ScreenOS version is 5.4.0, 6.2.0, or 6.3.0 (or any 5.4.x, 6.2.x, or 6.3.x variant within these branches)
-
Verify Ping of Death screen protection statusUse the CLI command to display the screen protection configuration (for example, 'get screen' or 'show security screen') and look for the Ping of Death (pod) screen protection settingAffected if Ping of Death screen protection is disabled or not listed as an active screen option
A user is affected if their device is a NetScreen 5200 or 5400, or runs ScreenOS 5.4.0, 6.2.0, or 6.3.0, AND the Ping of Death screen protection feature is currently disabled.
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 dataEnable the Ping of Death screen protection feature on affected NetScreen devices, or upgrade to a patched version of ScreenOS that addresses this vulnerability.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6958 — 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-2013-6958 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