LiveActive security incident?Get immediate response
CVE Record

CVE-2019-0043: Junos OS: RPD process crashes upon receipt of a specific SNMP packet

In MPLS environments, receipt of a specific SNMP packet may cause the routing protocol daemon (RPD) process to crash and restart. By continuously sending a specially crafted SNMP packet, an attacker can repetitively crash the RPD process causing prolonged denial of service. No other Juniper Networks products or platforms are affected by this issue. Affected releases are Juniper Networks Junos OS : 12.1X46 versions prior to 12.1X46-D77 on SRX Series; 12.3 versions prior to 12.3R12-S10; 12.3X48 versions prior to 12.3X48-D75 on SRX Series; 14.1X53 versions prior to 14.1X53-D48 on EX/QFX series; 15.1 versions prior to 15.1R4-S9, 15.1R7-S2; 15.1F6 versions prior to 15.1F6-S11; 15.1X49 versions prior to 15.1X49-D141, 15.1X49-D144, 15.1X49-D150 on SRX Series; 15.1X53 versions prior to 15.1X53-D234 on QFX5200/QFX5110 Series; 15.1X53 versions prior to 15.1X53-D68 on QFX10K Series; 15.1X53 versions prior to 15.1X53-D471, 15.1X53-D490 on NFX Series; 15.1X53 versions prior to 15.1X53-D590 on EX2300/EX3400 Series; 15.1X54 on ACX Series; 16.1 versions prior to 16.1R3-S10, 16.1R4-S11, 16.1R6-S5, 16.1R7; 16.1X65 versions prior to 16.1X65-D48; 16.2 versions prior to 16.2R2-S6; 17.1 versions prior to 17.1R2-S8, 17.1R3; 17.2 versions prior to 17.2R1-S7, 17.2R3; 17.2X75 versions prior to 17.2X75-D92, 17.2X75-D102, 17.2X75-D110; 17.3 versions prior to 17.3R3; 17.4 versions prior to 17.4R1-S4, 17.4R2; 18.1 versions prior to 18.1R1-S1, 18.1R2-S1, 18.1R3; 18.2X75 versions prior to 18.2X75-D10.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some Juniper Junos OS devices in MPLS environments can have their routing daemon crash after receiving a specific SNMP packet. Repeated packets could keep routing unstable and cause a prolonged denial of service. The issue is availability-only, but routing outages can directly affect business connectivity.

Executive priority

Treat as a high-priority network availability issue for MPLS environments. It does not indicate data theft, but repeated routing daemon crashes can disrupt business connectivity. Prioritize exposed Juniper infrastructure that supports critical network paths.

Technical view

CVE-2019-0043 is a Junos OS RPD crash condition triggered by a specific SNMP packet in MPLS environments. CVSS 3.0 is 7.5: network-reachable, low complexity, no privileges, no user interaction, high availability impact, no confidentiality or integrity impact. CWE-404 is listed.

Likely exposure

Exposure is most likely on Juniper SRX, EX, QFX, ACX, and NFX devices running the listed vulnerable Junos OS releases in MPLS environments where SNMP can reach the device. The bundle states no other Juniper products or platforms are affected.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The described attack condition is repeated delivery of a specific SNMP packet causing repeated RPD crashes and restart cycles. Evidence is sufficient for denial-of-service risk, not for confirmed exploitation in the wild.

Researcher notes

The key scoping constraints are Junos OS, MPLS environment, specific affected release trains, and SNMP packet handling leading to RPD crash. The source bundle provides fixed-version thresholds but does not provide exploit proof, packet details, or evidence of active exploitation.

Mitigation direction

  • Identify Junos OS devices running affected release trains listed in the advisory.
  • Prioritize upgrades to fixed Junos OS releases named by Juniper.
  • Check Juniper JSA10935 for current vendor guidance and any operational workarounds.
  • Restrict SNMP reachability to authorized management paths where consistent with existing policy.
  • Monitor routing daemon restarts until vulnerable systems are upgraded.

Validation and detection

  • Inventory Junos OS version, platform family, and MPLS use across network devices.
  • Compare installed versions with the affected and fixed releases in JSA10935.
  • Review SNMP exposure for affected devices without testing exploit traffic.
  • Check logs and monitoring for unexpected RPD restarts or routing instability.
  • Confirm post-upgrade versions are at or beyond Juniper fixed releases.
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-404: 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-0043 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
High
CVSS
7.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/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
7.5CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.5High
CVSS 3.0 vector shape for CVE-2019-0043Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/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 OS12.1X46, 12.3X48, 15.1X49Listed
Juniper NetworksJunos OS12.3, 15.1, 15.1F6, 16.1, 16.1X65, 16.2, 17.1, 17.2, 17.2X75, 17.3, 17.4, 18.1, 18.2X75Listed
Juniper NetworksJunos OS14.1X53Listed
Juniper NetworksJunos OS15.1X53Listed
Juniper NetworksJunos OS15.1X53Listed
Juniper NetworksJunos OS15.1X53Listed
Juniper NetworksJunos OS15.1X53Listed
Juniper NetworksJunos OS15.1X54Listed
Weakness

CWE details

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

CWE-404 · source CWE mapping

Improper Resource Shutdown or Release

Improper Resource Shutdown or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.