English
Français
Light
Dark
System

CVEFind - Alertes CVE

Restez informé en continue
Créer un compte Ouvrez un compte Simple et Gratuit Se connecter Gérez vos alertes

CVE-2023-28968 : Détail

CVE-2023-28968

5.3
/
MEDIUM
0.1%V3
Network
2023-04-16 22:00 +00:00
2024-08-02 13:51 +00:00
CVE.org
NVD

Alerte pour un CVE

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

Descriptions

Junos OS: SRX Series: Policies that rely on JDPI-Decoder actions may fail open

An Improperly Controlled Sequential Memory Allocation vulnerability in the Juniper Networks Deep Packet Inspection-Decoder (JDPI-Decoder) Application Signature component of Junos OS's AppID service on SRX Series devices will stop the JDPI-Decoder from identifying dynamic application traffic, allowing an unauthenticated network-based attacker to send traffic to the target device using the JDPI-Decoder, designed to inspect dynamic application traffic and take action upon this traffic, to instead begin to not take action and to pass the traffic through. An example session can be seen by running the following command and evaluating the output. user@device# run show security flow session source-prefix
extensive Session ID: , Status: Normal, State: Active Policy name: Dynamic application: junos:UNKNOWN, <<<<< LOOK HERE Please note, the JDPI-Decoder and the AppID SigPack are both affected and both must be upgraded along with the operating system to address the matter. By default, none of this is auto-enabled for automatic updates. This issue affects: Juniper Networks any version of the JDPI-Decoder Engine prior to version 5.7.0-47 with the JDPI-Decoder enabled using any version of the AppID SigPack prior to version 1.550.2-31 (SigPack 3533) on Junos OS on SRX Series: All versions prior to 19.1R3-S10; 19.2 versions prior to 19.2R3-S7; 19.3 versions prior to 19.3R3-S8; 19.4 versions prior to 19.4R3-S11; 20.1 version 20.1R1 and later versions prior to 20.2R3-S7; 20.3 version 20.3R1 and later versions prior to 20.4R3-S6; 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-S3; 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.4R3-S11, 20.2R3-S7, 20.4R3-S6, 21.1R3-S5, 21.2R3-S4, 21.3R3-S3, 21.4R3-S3, 22.1R3-S1, 22.2R2-S1, 22.2R3, 22.3R1-S2, 22.3R2, 22.4R1, and all subsequent releases. Please note: Prior to Junos OS: 21.2R3-S4, 21.3R3-S3, 21.3R3-S3, 21.4R3-S3, 22.1R3-S1, 22.2R2-S1, 22.2R3, 22.3R2, 22.4R1, and all subsequent releases SOF is incorrectly offloading short-lived flows leading to early exhaustion of NP memory, reducing overall device performance. Customers should review PRSearch PR1692100 for such details in conjunction with this advisory. Customers may choose to enable automatic updates for IDP or manually update the IDP security package to receive the fixes. To manually download the IDP signatures: a. Download the IDP security-package on the device: request security idp security-package download b. Check the status of the download: request security idp security-package download status c. Install the IDP security-package on the device: request security idp security-package install d. Check the status of the installation: request security idp security-package install status To enabled automatic update review the instuctions located at: https://supportportal.juniper.net/s/article/SRX-How-to-update-IDP-signature-database-automatically-on-a-SRX == When using AppID only: request services application-identification download request services application-identification download status request services application-identification install request services application-identification install status Or enable auto-update for AppID: [edit] user# set services application-identification download automatic ? Possible completions: interval Attempt to download new application package (hours) start-time Start time(MM-DD.hh:mm / YYYY-MM-DD.hh:mm:ss) Note: This updated signature package is not compatible with v4 engines.

Informations

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-1325 Improperly Controlled Sequential Memory Allocation
The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
CWE-770 Allocation of Resources Without Limits or Throttling
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.

Metrics

Metric Score Sévérité CVSS Vecteur Source
V3.1 5.3 MEDIUM CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.

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.

Low

Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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.

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>>Appid_service_sigpack >> Version To (excluding) 1.550.2-31

Juniper>>Jdpi-decoder_engine >> Version To (excluding) 5.7.0-47

Juniper>>Srx100 >> Version -

Juniper>>Srx110 >> Version -

Juniper>>Srx1400 >> Version -

Juniper>>Srx1500 >> Version -

Juniper>>Srx210 >> Version -

Juniper>>Srx220 >> Version -

Juniper>>Srx240 >> Version -

Juniper>>Srx240h2 >> Version -

Juniper>>Srx240m >> Version -

Juniper>>Srx300 >> Version -

Juniper>>Srx320 >> Version -

Juniper>>Srx340 >> Version -

Juniper>>Srx3400 >> Version -

Juniper>>Srx345 >> Version -

Juniper>>Srx3600 >> Version -

Juniper>>Srx380 >> Version -

Juniper>>Srx4000 >> Version -

Juniper>>Srx4100 >> Version -

Juniper>>Srx4200 >> Version -

Juniper>>Srx4600 >> Version -

Juniper>>Srx5000 >> Version -

Juniper>>Srx5400 >> Version -

Juniper>>Srx550 >> Version -

Juniper>>Srx550_hm >> Version -

Juniper>>Srx550m >> Version -

Juniper>>Srx5600 >> Version -

Juniper>>Srx5800 >> Version -

Juniper>>Srx650 >> Version -

Configuraton 0

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

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

Juniper>>Junos >> Version 21.1

Juniper>>Junos >> Version 21.1

Juniper>>Junos >> Version 21.1

Juniper>>Junos >> Version 21.1

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

Juniper>>Junos >> Version 22.3

Juniper>>Srx100 >> Version -

Juniper>>Srx110 >> Version -

Juniper>>Srx1400 >> Version -

Juniper>>Srx1500 >> Version -

Juniper>>Srx210 >> Version -

Juniper>>Srx220 >> Version -

Juniper>>Srx240 >> Version -

Juniper>>Srx240h2 >> Version -

Juniper>>Srx240m >> Version -

Juniper>>Srx300 >> Version -

Juniper>>Srx320 >> Version -

Juniper>>Srx340 >> Version -

Juniper>>Srx3400 >> Version -

Juniper>>Srx345 >> Version -

Juniper>>Srx3600 >> Version -

Juniper>>Srx380 >> Version -

Juniper>>Srx4000 >> Version -

Juniper>>Srx4100 >> Version -

Juniper>>Srx4200 >> Version -

Juniper>>Srx4600 >> Version -

Juniper>>Srx5000 >> Version -

Juniper>>Srx5400 >> Version -

Juniper>>Srx550 >> Version -

Juniper>>Srx550_hm >> Version -

Juniper>>Srx550m >> Version -

Juniper>>Srx5600 >> Version -

Juniper>>Srx5800 >> Version -

Juniper>>Srx650 >> Version -

References

https://supportportal.juniper.net/JSA70592
Tags : Mitigation, Vendor Advisory

Plus d'informations
Cliquez sur le bouton à gauche (OFF), pour autoriser l'inscription de cookie améliorant les fonctionnalités du site. Cliquez sur le bouton à gauche (Tout accepter), pour ne plus autoriser l'inscription de cookie améliorant les fonctionnalités du site.