Skip to content

An Improper Validation of Syntactic Correctness of Input...

High severity Unreviewed Published Apr 12, 2024 to the GitHub Advisory Database • Updated Apr 26, 2024

Package

No package listedSuggest a package

Affected versions

Unknown

Patched versions

Unknown

Description

An Improper Validation of Syntactic Correctness of Input vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based, unauthenticated attacker to cause a Denial of Service (DoS).

If a BGP update is received over an established BGP session which contains a tunnel encapsulation attribute with a specifically malformed TLV, rpd will crash and restart.

This issue affects Juniper Networks
Junos OS:

  • 20.4 versions 20.4R1 and later versions earlier than 20.4R3-S9;
  • 21.2 versions earlier than 21.2R3-S7;
  • 21.3 versions earlier than 21.3R3-S5;
  • 21.4 versions earlier than 21.4R3-S5;
  • 22.1 versions earlier than 22.1R3-S4;
  • 22.2 versions earlier than 22.2R3-S3;
  • 22.3 versions earlier than 22.3R3-S1;
  • 22.4 versions earlier than 22.4R3;
  • 23.2 versions earlier than 23.2R1-S2, 23.2R2;

Junos OS Evolved:

  • 20.4-EVO versions 20.4R1-EVO and later versions earlier than 20.4R3-S9-EVO;
  • 21.2-EVO versions earlier than 21.2R3-S7-EVO;
  • 21.3-EVO versions earlier than 21.3R3-S5-EVO;
  • 21.4-EVO versions earlier than 21.4R3-S5-EVO;
  • 22.1-EVO versions earlier than 22.1R3-S4-EVO;
  • 22.2-EVO versions earlier than 22.2R3-S3-EVO;
  • 22.3-EVO versions earlier than 22.3R3-S1-EVO;
  • 22.4-EVO versions earlier than 22.4R3-EVO;
  • 23.2-EVO versions earlier than 23.2R1-S2-EVO, 23.2R2-EVO;

This issue does not affect Juniper Networks

  • Junos OS versions earlier than 20.4R1;
  • Junos OS Evolved versions earlier than 20.4R1-EVO.

This is a related but separate issue than the one described in JSA79095.

References

Published by the National Vulnerability Database Apr 12, 2024
Published to the GitHub Advisory Database Apr 12, 2024
Last updated Apr 26, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2024-21598

GHSA ID

GHSA-p5h3-wwqf-f5rv

Source code

No known source code

Dependabot alerts are not supported on this advisory because it does not have a package from a supported ecosystem with an affected and fixed version.

Learn more about GitHub language support

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.