CVE-2019-0068
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 · uneditedThe SRX flowd process, responsible for packet forwarding, may crash and restart when processing specific multicast packets. By continuously sending the specific multicast packets, an attacker can repeatedly crash the flowd process causing a sustained Denial of Service. This issue affects Juniper Networks Junos OS on SRX Series: 12.3X48 versions prior to 12.3X48-D90; 15.1X49 versions prior to 15.1X49-D180; 17.3 versions; 17.4 versions prior to 17.4R2-S5, 17.4R3; 18.1 versions prior to 18.1R3-S6; 18.2 versions prior to 18.2R2-S4, 18.2R3; 18.3 versions prior to 18.3R2-S1, 18.3R3; 18.4 versions prior to 18.4R2; 19.1 versions prior to 19.1R1-S1, 19.1R2.
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 vulnerability in the SRX flowd process on Juniper Junos OS allows remote attackers to cause a denial of service by sending specific multicast packets that crash the flowd process, which handles packet forwarding. Repeated exploitation leads to sustained service disruption.
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= 12.3x48= 15.1x49= 17.3= 17.4= 18.1= 18.2= 18.3= 18.4= 19.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 device modelRun 'show chassis hardware' or 'show system information' to confirm the device is a Juniper SRX seriesAffected if Device is not an SRX series (flowd process is specific to SRX)
-
Check Junos OS versionRun 'show version' to obtain the installed Junos versionAffected if Version matches 12.3X48, 15.1X49, 17.3, 17.4, 18.1, 18.2, 18.3, 18.4, or 19.1 (any build within these release families)
-
Verify flowd process is runningRun 'show system processes' or check process status via 'cli> show system processes extensive | match flowd'Affected if flowd process is active and handling packet forwarding
-
Check if multicast is processedRun 'show multicast interface' or 'show multicast route' to see if multicast routing or IGMP proxy is enabledAffected if Multicast traffic processing or IGMP proxy is configured on the device
-
Inspect for recent flowd crashesRun 'show system crash' or check /var/log/messages for flowd core dumps and restartsAffected if flowd process has recently crashed or generated core dump files
Device is affected if it is an SRX series running a vulnerable Junos version (12.3X48, 15.1X49, 17.3-17.4, 18.1-18.4, or 19.1) and processing multicast traffic, with possible 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 OS to the specified patched versions (12.3X48-D90+, 15.1X49-D180+, 17.4R2-S5+, 17.4R3+, 18.1R3-S6+, 18.2R2-S4+, 18.2R3+, 18.3R2-S1+, 18.3R3+, 18.4R2+, 19.1R1-S1+, or 19.1R2+) to resolve the vulnerability.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,016.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0068 — 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-2019-0068 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