CVE-2023-4481 : Détail

CVE-2023-4481

7.5
/
Haute
A03-Injection
1.3%V4
Network
2023-08-31
23h46 +00:00
2024-10-02
15h09 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

Junos OS and Junos OS Evolved: A crafted BGP UPDATE message allows a remote attacker to de-peer (reset) BGP sessions (CVE-2023-4481)

An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). When certain specific crafted BGP UPDATE messages are received over an established BGP session, one BGP session may be torn down with an UPDATE message error, or the issue may propagate beyond the local system which will remain non-impacted, but may affect one or more remote systems. This issue is exploitable remotely as the crafted UPDATE message can propagate through unaffected systems and intermediate BGP speakers. Continuous receipt of the crafted BGP UPDATE messages will create a sustained Denial of Service (DoS) condition for impacted devices. This issue affects eBGP and iBGP, in both IPv4 and IPv6 implementations. This issue requires a remote attacker to have at least one established BGP session. Improper Input Validation, Denial of Service vulnerability in Juniper Networks, Inc. Junos OS (BGP, rpd modules), Juniper Networks, Inc. Junos OS Evolved (BGP, rpd modules) allows Fuzzing.This issue affects  Junos OS:  * All versions before 20.4R3-S10, * from 21.1R1 through 21.*, * from 21.2 before 21.2R3-S5, * from 21.3 before 21.3R3-S5, * from 21.4 before 21.4R3-S7 (unaffected from 21.4R3-S5, affected from 21.4R3-S6) * from 22.1 before 22.1R3-S4, * from 22.2 before 22.2R3-S3, * from 22.3 before 22.3R3-S1, * from 22.4 before 22.4R3, * from 23.2 before 23.2R2. Junos OS Evolved: * All versions before 20.4R3-S10-EVO, * from 21.2-EVO before 21.2R3-S7-EVO, * from 21.3-EVO before 21.3R3-S5-EVO, * from 21.4-EVO before 21.4R3-S5-EVO, * from 22.1-EVO before 22.1R3-S4-EVO, * from 22.2-EVO before 22.2R3-S3-EVO, * from 22.3-EVO before 22.3R3-S1-EVO, * from 22.4-EVO before 22.4R3-EVO, * from 23.2-EVO before 23.2R2-EVO.

Solutions du CVE

The following software releases have been updated to resolve this specific issue: Junos OS: 20.4R3-S10, 21.2R3-S7, 21.3R3-S5, 21.4R3-S5 or 21.4R3-S7, 22.1R3-S4, 22.2R3-S3, 22.3R3-S1, 22.4R3, 23.2R2, 23.3R2, 23.4R1, and all subsequent releases Note: except for Junos OS 21.4R3-S6 which is affected and unfixed. Junos OS Evolved: 20.4R3-S10-EVO, 21.2R3-S7-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S3-EVO, 22.3R3-S1-EVO, 22.4R3-EVO, 23.2R2-EVO, 23.4R1-EVO, and all subsequent releases. It is important that customers implement the workaround in addition to taking any updated software as these crafted UPDATE messages may be propagated to other devices even if non-impacted locally, thereby protecting the network by stopping the propagation of these crafted UPDATE messages. The workaround is to configure BGP error tolerance by way of:   [ protocols bgp bgp-error-tolerance ... ] Additional details can be found at https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/bgp-error-messages.h... https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/bgp-error-messages.html Juniper considers configuring this option to be a Best Common Practice (BCP) as it not only prevents this issue from happening, but protects against similar issues as well. This issue is being tracked as PR 1709837 https://prsearch.juniper.net/problemreport/PR1709837  which is visible on the Customer Support website. Note: Juniper SIRT's policy https://kb.juniper.net/KB16765  is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-20 Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE Other No informations.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.1 7.5 HIGH CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

None

There is no loss of confidentiality within the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Juniper>>Junos >> Version To (excluding) 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 21.1

Juniper>>Junos >> Version 21.1

Juniper>>Junos >> Version 21.1

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.3

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 21.4

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.1

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.2

Juniper>>Junos >> Version 22.3

Juniper>>Junos >> Version 22.3

Juniper>>Junos >> Version 22.3

Juniper>>Junos >> Version 22.3

Juniper>>Junos >> Version 22.3

Juniper>>Junos >> Version 22.3

Juniper>>Junos >> Version 22.3

Juniper>>Junos >> Version 22.3

Juniper>>Junos >> Version 22.4

Juniper>>Junos >> Version 22.4

Juniper>>Junos >> Version 22.4

Juniper>>Junos >> Version 22.4

Juniper>>Junos >> Version 22.4

Juniper>>Junos >> Version 22.4

Juniper>>Junos >> Version 22.4

Juniper>>Junos >> Version 23.2

Juniper>>Junos >> Version 23.2

Juniper>>Junos >> Version 23.2

Juniper>>Junos >> Version 23.2

Configuraton 0

Juniper>>Junos_os_evolved >> Version To (excluding) 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 20.4

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.2

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.3

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 21.4

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.1

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.2

Juniper>>Junos_os_evolved >> Version 22.3

Juniper>>Junos_os_evolved >> Version 22.3

Juniper>>Junos_os_evolved >> Version 22.3

Juniper>>Junos_os_evolved >> Version 22.3

Juniper>>Junos_os_evolved >> Version 22.3

Juniper>>Junos_os_evolved >> Version 22.3

Juniper>>Junos_os_evolved >> Version 22.3

Juniper>>Junos_os_evolved >> Version 22.3

Juniper>>Junos_os_evolved >> Version 22.4

Juniper>>Junos_os_evolved >> Version 22.4

Juniper>>Junos_os_evolved >> Version 22.4

Juniper>>Junos_os_evolved >> Version 22.4

Juniper>>Junos_os_evolved >> Version 22.4

Juniper>>Junos_os_evolved >> Version 22.4

Juniper>>Junos_os_evolved >> Version 22.4

Juniper>>Junos_os_evolved >> Version 22.4

Juniper>>Junos_os_evolved >> Version 23.2

Juniper>>Junos_os_evolved >> Version 23.2

Juniper>>Junos_os_evolved >> Version 23.2

Juniper>>Junos_os_evolved >> Version 23.2

Références

https://kb.juniper.net/JSA72510
Tags : vendor-advisory
https://www.rfc-editor.org/rfc/rfc7606
Tags : technical-description
https://www.rfc-editor.org/rfc/rfc4271
Tags : technical-description
Les informations affichées sur CVE Find proviennent de plusieurs sources de référence rigoureusement sélectionnées. Les données CVE sont fournies par MITRE Corporation et la National Vulnerability Database (NVD). Le catalogue des vulnérabilités activement exploitées (KEV) provient de la Cybersecurity and Infrastructure Security Agency (CISA), tandis que les scores EPSS sont issus de FIRST.org. Enfin, les données relatives aux faiblesses logicielles (CWE) et aux schémas d'attaque courants (CAPEC) sont maintenues par MITRE Corporation, et les informations sur les configurations logicielles et matérielles (CPE) proviennent du NVD.