CVE-2025-21590 : Detail

CVE-2025-21590

6.7
/
Medium
A04-Insecure Design
2.07%V3
Local
2025-03-12
13h59 +00:00
2025-03-14
16h15 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Junos OS: An local attacker with shell access can execute arbitrary code

An Improper Isolation or Compartmentalization vulnerability in the kernel of Juniper Networks Junos OS allows a local attacker with high privileges to compromise the integrity of the device. A local attacker with access to the shell is able to inject arbitrary code which can compromise an affected device. This issue is not exploitable from the Junos CLI. This issue affects Junos OS:  * All versions before 21.2R3-S9, * 21.4 versions before 21.4R3-S10,  * 22.2 versions before 22.2R3-S6,  * 22.4 versions before 22.4R3-S6,  * 23.2 versions before 23.2R2-S3,  * 23.4 versions before 23.4R2-S4, * 24.2 versions before 24.2R1-S2, 24.2R2.

CVE Solutions

The following software releases have been updated to resolve this specific issue: 21.2R3-S9*, 21.4R3-S10, 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S4*, 24.2R1-S2, 24.2R2, 24.4R1, and all subsequent releases. * Future Release Note: The complete list of resolved platforms is still under investigation.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-653 Improper Isolation or Compartmentalization
The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.

Metrics

Metrics Score Severity CVSS Vector Source
V4.0 6.7 MEDIUM CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Base: Exploitabilty Metrics

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

Attack Vector

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

Local

The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).

Attack Complexity

This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit.

Low

The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.

Attack Requirements

This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack.

None

The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.

Privileges Required

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

High

The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.

User Interaction

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

None

The vulnerable system can be exploited without interaction from any human user, other than the attacker. Examples include: a remote attacker is able to send packets to a target system a locally authenticated attacker executes code to elevate privileges

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability. 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 managed by the system due to a successfully exploited vulnerability.

None

There is no loss of confidentiality within the Vulnerable System.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability.

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 Vulnerable System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Vulnerable System.

Availability Impact

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

None

There is no impact to availability within the Vulnerable System.

Sub Confidentiality Impact

Negligible

There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.

Sub Integrity Impact

None

There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.

Sub Availability Impact

None

There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Threat Metrics

The Threat metrics measure the current state of exploit techniques or code availability for a vulnerability.

Environmental Metrics

These metrics enable the consumer analyst to customize the resulting score depending on the importance of the affected IT asset to a user’s organization, measured in terms of complementary/alternative security controls in place, Confidentiality, Integrity, and Availability. The metrics are the modified equivalent of Base metrics and are assigned values based on the system placement within organizational infrastructure.

Supplemental Metrics

Supplemental metric group provides new metrics that describe and measure additional extrinsic attributes of a vulnerability. While the assessment of Supplemental metrics is provisioned by the provider, the usage and response plan of each metric within the Supplemental metric group is determined by the consumer.

V3.1 4.4 MEDIUM CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

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.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

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.

High

The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files.

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.

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.

None

There is no impact to availability within the impacted component.

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.

CISA KEV (Known Exploited Vulnerabilities)

Vulnerability name : Juniper Junos OS Improper Isolation or Compartmentalization Vulnerability

Required action : Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Known To Be Used in Ransomware Campaigns : Unknown

Added : 2025-03-12 23h00 +00:00

Action is due : 2025-04-02 22h00 +00:00

Important information
This CVE is identified as vulnerable and poses an active threat, according to the Catalog of Known Exploited Vulnerabilities (CISA KEV). The CISA has listed this vulnerability as actively exploited by cybercriminals, emphasizing the importance of taking immediate action to address this flaw. It is imperative to prioritize the update and remediation of this CVE to protect systems against potential cyberattacks.

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Products Mentioned

Configuraton 0

Juniper>>Junos >> Version To (including) 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.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

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

    Juniper>>Junos >> Version 22.2

    Juniper>>Junos >> Version 22.2

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

          Juniper>>Junos >> Version 23.2

          Juniper>>Junos >> Version 23.2

          Juniper>>Junos >> Version 23.2

            Juniper>>Junos >> Version 23.4

            Juniper>>Junos >> Version 23.4

            Juniper>>Junos >> Version 23.4

            Juniper>>Junos >> Version 23.4

            Juniper>>Junos >> Version 23.4

            Juniper>>Junos >> Version 23.4

            Juniper>>Junos >> Version 23.4

              Juniper>>Junos >> Version 23.4

                Juniper>>Junos >> Version 23.4

                  Juniper>>Junos >> Version 24.2

                  Juniper>>Junos >> Version 24.2

                  Juniper>>Junos >> Version 24.2

                  Juniper>>Junos >> Version 24.2

                    Juniper>>Junos >> Version 24.2

                    References