CVE-2014-3822
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 Junos 11.4 before 11.4R8, 12.1 before 12.1R5, 12.1X44 before 12.1X44-D20, 12.1X45 before 12.1X45-D15, 12.1X46 before 12.1X46-D10, and 12.1X47 before 12.1X47-D10 on SRX Series devices, allows remote attackers to cause a denial of service (flowd crash) via a malformed packet, related to translating IPv6 to IPv4.
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 confidenceThis is a denial of service vulnerability in Juniper Junos SRX Series devices where malformed packets during IPv6-to-IPv4 translation cause the flowd (flow daemon) process to crash, requiring device restart to restore network security functionality.
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= 11.4= 12.1= 12.1x44= 12.1x45= 12.1x46= 12.1x47all versionsall versionsall versionsall versionsall versionsall 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
- High
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:H/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 Junos software versionRun 'show version' or 'show version detail' command on the SRX deviceAffected if The version matches 11.4, 12.1, 12.1X44, 12.1X45, 12.1X46, or 12.1X47 (without the fixed releases R8, D20, D15, D10, D10)
-
Identify the SRX hardware modelRun 'show chassis hardware' or check the model name from 'show version' outputAffected if The model is Srx100, Srx110, Srx1400, Srx210, Srx220, Srx240, or Srx3400 (these are affected at all versions)
-
Check if IPv6-to-IPv4 translation is enabledRun 'show nat' or 'show services nat' commands to identify NAT64/46 configuration; also check 'show configuration | match nat64' or 'show configuration services nat'Affected if IPv6-to-IPv4 translation (NAT64) policy or rule is configured and active on the device
-
Verify flowd daemon statusRun 'show system processes' or 'show system processes extensive | match flowd' to check if flowd is runningAffected if The flowd process has crashed (not running) or is restarting repeatedly, especially after IPv6 traffic traverses the NAT64 translation
You are affected if you run an affected Junos version or SRX model AND have IPv6-to-IPv4 translation enabled, with evidence of flowd crashes.
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 dataUpgrade Junos to versions 11.4R8, 12.1R5, 12.1X44-D20, 12.1X45-D15, 12.1X46-D10, 12.1X47-D10 or later. Until patching is possible, consider restricting untrusted network access to SRX devices.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3822 — 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-2014-3822 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