LiveActive security incident?Get immediate response
CVE Record

CVE-2019-0068: Junos OS: SRX Series: Denial of Service vulnerability in flowd due to multicast packets

The 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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-0068 can make Juniper SRX firewalls repeatedly lose packet-forwarding service when they process specific multicast packets. The impact is availability only, but sustained crashes of flowd can disrupt traffic through affected security gateways.

Executive priority

Treat this as a moderate operational resilience issue. It does not expose data, but it can interrupt firewall packet forwarding and network availability if reachable by an adjacent attacker.

Technical view

Affected Junos OS releases on SRX Series can crash and restart the flowd packet-forwarding process while handling specific multicast packets. CVSS 3.1 is 6.5: adjacent network, low complexity, no privileges, no user interaction, high availability impact, no confidentiality or integrity impact.

Likely exposure

Exposure is limited to Juniper SRX Series devices running the listed vulnerable Junos OS trains from 12.3X48 through 19.1. Risk depends on whether an attacker can send relevant multicast traffic from an adjacent network path.

Exploitation context

The provided sources describe a denial-of-service condition caused by continuously sending specific multicast packets. The CVE is not in CISA KEV, and the bundle provides no evidence of active exploitation.

Researcher notes

The issue maps to CWE-754 and affects flowd handling of unusual multicast packet conditions. Public details in the bundle are limited; avoid assuming exploit tooling, broader Juniper product impact, or mitigations beyond Juniper guidance.

Mitigation direction

  • Upgrade SRX devices to fixed Junos OS releases listed in Juniper JSA10968.
  • Prioritize SRX firewalls on exposed or high-availability network segments.
  • Check Juniper advisory JSA10968 for the current vendor guidance before scheduling remediation.
  • Monitor affected devices for recurring flowd crashes until upgrades are complete.

Validation and detection

  • Inventory Juniper SRX devices and identify Junos OS versions in the affected trains.
  • Confirm each SRX runs a fixed release or newer for its Junos OS branch.
  • Review device logs for repeated flowd crashes or restarts involving multicast traffic.
  • Document any remaining vulnerable SRX systems and their remediation owner.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-754: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-0068 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2019-0068Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OS17.3, 12.3X48, 15.1X49, 17.4, 18.1, 18.2, 18.3, 18.4, 19.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-754 · source CWE mapping

Improper Check for Unusual or Exceptional Conditions

Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.