CVE-2023-28972

Score / Sévérité

6.8

MEDIUM

OWSAP

A01-Broken Access Control

EPSS

0.08%V3

Vecteur

Physical

Publié

2023-04-16 22:00 +00:00

Dernière modif.

2024-08-02 13:51 +00:00

Liens officiels

CVE.org

NVD

Alerte pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.

Gestion des alertes

Liste des Alertes

Alerte pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.

Critères appliqués l'envoi de l'alerte : par rapport à la dernière alerte envoyée + différences au niveau de CISA, EPSS, CVSS, CWE, Solutions, CPE.

Paramètres

Vous pouvez sécifier un titre qui sera récupéré dans les alertes qui seront envoyées.

Spécifiez ici un CVE ID comme CVE-2024-1234

Planificiations

Mois

Prochaine exécution calculée

Jour

Jour de la semaine

Heure

Minute

Date de création

Dernière exécution

Prochaine exécution

Fonctionnalité nécessitant une connexion

Cette fonctionnalité qui vous permet de recevoir des alertes, n'est active que lorsque vous êtes connecté à votre compte.

Descriptions

Junos OS: NFX Series: 'set system ports console insecure' allows root password recovery

An Improper Link Resolution Before File Access vulnerability in console port access of Juniper Networks Junos OS on NFX Series allows an attacker to bypass console access controls. When "set system ports console insecure" is enabled, root login is disallowed for Junos OS as expected. However, the root password can be changed using "set system root-authentication plain-text-password" on NFX Series systems, leading to a possible administrative bypass with physical access to the console. Password recovery, changing the root password from a console, should not have been allowed from an insecure console. This is similar to the vulnerability described in CVE-2019-0035 but affects different platforms and in turn requires a different fix. This issue affects Juniper Networks Junos OS on NFX Series: 19.2 versions prior to 19.2R3-S7; 19.3 versions prior to 19.3R3-S8; 19.4 versions prior to 19.4R3-S12; 20.2 versions prior to 20.2R3-S8; 20.4 versions prior to 20.4R3-S7; 21.1 versions prior to 21.1R3-S5; 21.2 versions prior to 21.2R3-S4; 21.3 versions prior to 21.3R3-S3; 21.4 versions prior to 21.4R3-S2; 22.1 versions prior to 22.1R3-S1; 22.2 versions prior to 22.2R2-S1, 22.2R3; 22.3 versions prior to 22.3R1-S2, 22.3R2.

Solutions

The following software releases have been updated to resolve this specific issue: 19.2R3-S7, 19.3R3-S8, 19.4R3-S12, 20.4R3-S7, 21.1R3-S5, 21.2R3-S4, 21.3R3-S3, 21.4R3-S2, 22.1R3-S1, 22.2R2-S1, 22.2R3, 22.3R1-S2, 22.3R2, 22.4R1, and all subsequent releases.

Informations

Faiblesses connexes

CWE-ID	Nom de la faiblesse	Source
CWE-59	Improper Link Resolution Before File Access ('Link Following') The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

Metrics

Metric	Score	Sévérité	CVSS Vecteur	Source
V3.1	6.8	MEDIUM	CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H More informations 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. Physical The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief (e.g., evil maid attack1) or persistent. An example of such an attack is a cold boot attack in which an attacker gains access to disk encryption keys after physically accessing the target system. Other examples include peripheral attacks via FireWire/USB Direct Memory Access (DMA). 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. High There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server. Integrity Impact This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. High There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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.

EPSS Score

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.

EPSS Percentile

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 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3 (Open CPE detail)