CVE-2022-25869

Score / Gravité

6.1

Moyen

Catégories

Cross-site Scripting

OWSAP

A03-Injection

EPSS

1.6%V4

Vecteur

Network

Publié

2022-07-15
20h02 +00:00

Modifié

2025-07-28
09h59 +00:00

Liens officiels

CVE.org

NVD

Notifications pour un CVE

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

Gestion des notifications

Liste des Notifications

Notifications 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 spécifier un titre qui sera récupéré dans les alertes qui seront envoyées.

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

Planifications

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

All versions of the package angular; all versions of the package angularjs.core; all versions of the package angularjs are vulnerable to Cross-site Scripting (XSS) due to insecure page caching in the Internet Explorer browser, which allows interpolation of

elements.                            </div>
                        </div>

<div class="card card-flush py-4">
                            <div class="card-header">
                                <div class="card-title">
                                    <h2>Informations du CVE</h2>
                                </div>
                            </div>
                            <div class="card-body pt-0">
                                            <h2 class="tw-h3">Faiblesses connexes</h2>

<div class="table-responsive">
                <table class="table table-striped gy-7 gs-7">
                    <thead>
                    <tr class="fw-semibold fs-6 text-gray-800 border-bottom border-gray-200">
                        <th><nobr>CWE-ID</nobr></th>
                        <th>Nom de la faiblesse</th>
                        <th>Source</th>
                    </tr>
                    </thead>
                    <tbody>
                                <tr>
                                    <td><nobr><a href="/fr/cwe/cwe-79.html">CWE-79</a></nobr></td>
                                    <td><b>Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')</b><br>The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.</td>
                                    <td></td>
                                </tr>
                </tbody>
            </table>
        </div>
            <div class="separator my-10"></div>

<h3>Métriques</h3>

<div class="table-responsive">
                <table class="table table-striped gy-7 gs-7">
                    <thead>
                    <tr class="fw-semibold fs-6 text-gray-800 border-bottom border-gray-200">
                        <th>Métriques</th>
                        <th>Score</th>
                        <th>Gravité</th>
                        <th>CVSS Vecteur</th>
                        <th>Source</th>
                    </tr>
                    </thead>
                    <tbody>
                    <tr>
                        <td>V3.1</td>
                        <td>4.2</td>
                        <td>MEDIUM</td>
                        <td>
                            CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P                                    <div class="m-0">
            <div class="d-flex align-items-center collapsible toggle mb-0 collapsed" data-bs-toggle="collapse" data-bs-target="#metric-175433816450273" aria-expanded="false">
                <div class="btn btn-sm btn-icon mw-20px btn-active-color-primary me-5">
                    <i class="ki-duotone ki-minus-square toggle-on text-primary fs-4">
                        <span class="path1"></span>
                        <span class="path2"></span>
                    </i>
                    <i class="ki-duotone ki-plus-square toggle-off fs-4">
                        <span class="path1"></span>
                        <span class="path2"></span>
                        <span class="path3"></span>
                    </i>
                </div>
                <span class="text-gray-700 cursor-pointer mb-0">More informations</span>
            </div>
            <div id="metric-175433816450273" class="fs-7 ms-1 collapse" style="">
                <div class="mb-4">
                    <div class="d-flex align-items-center ps-10 mb-n1">
                        <div class="text-gray-600 fs-7">
                            <h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Base: Exploitabilty Metrics</h4><p>The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.</p><div class='tw-h5' style='padding-left:10px'>Attack Vector</div><p style='padding-left:10px'>This metric reflects the context by which vulnerability exploitation is possible.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Network</p></div><div style='flex: 1;margin-left:5px;'><p>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).</p></div></div><div class='tw-h5' style='padding-left:10px'>Attack Complexity</div><p style='padding-left:10px'>This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>High</p></div><div style='flex: 1;margin-left:5px;'><p> successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.</p></div></div><div class='tw-h5' style='padding-left:10px'>Privileges Required</div><p style='padding-left:10px'>This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>None</p></div><div style='flex: 1;margin-left:5px;'><p>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.</p></div></div><div class='tw-h5' style='padding-left:10px'>User Interaction</div><p style='padding-left:10px'>This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Required</p></div><div style='flex: 1;margin-left:5px;'><p>Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Base: Scope Metrics</h4><p>The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.</p><div class='tw-h5' style='padding-left:10px'>Scope</div><p style='padding-left:10px'>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.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Unchanged</p></div><div style='flex: 1;margin-left:5px;'><p>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.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Base: Impact Metrics</h4><p>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.</p><div class='tw-h5' style='padding-left:10px'>Confidentiality Impact</div><p style='padding-left:10px'>This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Integrity Impact</div><p style='padding-left:10px'>This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>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.</p></div></div><div class='tw-h5' style='padding-left:10px'>Availability Impact</div><p style='padding-left:10px'>This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>None</p></div><div style='flex: 1;margin-left:5px;'><p>There is no impact to availability within the impacted component.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Temporal Metrics</h4><p>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.</p><div class='tw-h5' style='padding-left:10px'>Exploit Code Maturity</div><p style='padding-left:10px'>This metric measures the likelihood of the vulnerability being attacked, and is typically based on the current state of exploit techniques, exploit code availability, or active, “in-the-wild” exploitation.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Proof-of-Concept</p></div><div style='flex: 1;margin-left:5px;'><p>Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Environmental Metrics</h4><p>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.</p>                        </div>
                    </div>
                </div>
            </div>
        </div>
                        </td>
                        <td></td>
                    </tr>
                    <tr>
                        <td>V3.1</td>
                        <td>4.2</td>
                        <td>MEDIUM</td>
                        <td>
                            CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N                                    <div class="m-0">
            <div class="d-flex align-items-center collapsible toggle mb-0 collapsed" data-bs-toggle="collapse" data-bs-target="#metric-175433816450615" aria-expanded="false">
                <div class="btn btn-sm btn-icon mw-20px btn-active-color-primary me-5">
                    <i class="ki-duotone ki-minus-square toggle-on text-primary fs-4">
                        <span class="path1"></span>
                        <span class="path2"></span>
                    </i>
                    <i class="ki-duotone ki-plus-square toggle-off fs-4">
                        <span class="path1"></span>
                        <span class="path2"></span>
                        <span class="path3"></span>
                    </i>
                </div>
                <span class="text-gray-700 cursor-pointer mb-0">More informations</span>
            </div>
            <div id="metric-175433816450615" class="fs-7 ms-1 collapse" style="">
                <div class="mb-4">
                    <div class="d-flex align-items-center ps-10 mb-n1">
                        <div class="text-gray-600 fs-7">
                            <h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Base: Exploitabilty Metrics</h4><p>The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.</p><div class='tw-h5' style='padding-left:10px'>Attack Vector</div><p style='padding-left:10px'>This metric reflects the context by which vulnerability exploitation is possible.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Network</p></div><div style='flex: 1;margin-left:5px;'><p>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).</p></div></div><div class='tw-h5' style='padding-left:10px'>Attack Complexity</div><p style='padding-left:10px'>This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>High</p></div><div style='flex: 1;margin-left:5px;'><p> successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.</p></div></div><div class='tw-h5' style='padding-left:10px'>Privileges Required</div><p style='padding-left:10px'>This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>None</p></div><div style='flex: 1;margin-left:5px;'><p>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.</p></div></div><div class='tw-h5' style='padding-left:10px'>User Interaction</div><p style='padding-left:10px'>This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Required</p></div><div style='flex: 1;margin-left:5px;'><p>Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Base: Scope Metrics</h4><p>The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.</p><div class='tw-h5' style='padding-left:10px'>Scope</div><p style='padding-left:10px'>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.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Unchanged</p></div><div style='flex: 1;margin-left:5px;'><p>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.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Base: Impact Metrics</h4><p>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.</p><div class='tw-h5' style='padding-left:10px'>Confidentiality Impact</div><p style='padding-left:10px'>This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Integrity Impact</div><p style='padding-left:10px'>This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>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.</p></div></div><div class='tw-h5' style='padding-left:10px'>Availability Impact</div><p style='padding-left:10px'>This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>None</p></div><div style='flex: 1;margin-left:5px;'><p>There is no impact to availability within the impacted component.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Temporal Metrics</h4><p>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.</p><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Environmental Metrics</h4><p>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.</p>                        </div>
                    </div>
                </div>
            </div>
        </div>
                        </td>
                        <td>report@snyk.io</td>
                    </tr>
                    <tr>
                        <td>V3.1</td>
                        <td>6.1</td>
                        <td>MEDIUM</td>
                        <td>
                            CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N                                    <div class="m-0">
            <div class="d-flex align-items-center collapsible toggle mb-0 collapsed" data-bs-toggle="collapse" data-bs-target="#metric-175433816483869" aria-expanded="false">
                <div class="btn btn-sm btn-icon mw-20px btn-active-color-primary me-5">
                    <i class="ki-duotone ki-minus-square toggle-on text-primary fs-4">
                        <span class="path1"></span>
                        <span class="path2"></span>
                    </i>
                    <i class="ki-duotone ki-plus-square toggle-off fs-4">
                        <span class="path1"></span>
                        <span class="path2"></span>
                        <span class="path3"></span>
                    </i>
                </div>
                <span class="text-gray-700 cursor-pointer mb-0">More informations</span>
            </div>
            <div id="metric-175433816483869" class="fs-7 ms-1 collapse" style="">
                <div class="mb-4">
                    <div class="d-flex align-items-center ps-10 mb-n1">
                        <div class="text-gray-600 fs-7">
                            <h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Base: Exploitabilty Metrics</h4><p>The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.</p><div class='tw-h5' style='padding-left:10px'>Attack Vector</div><p style='padding-left:10px'>This metric reflects the context by which vulnerability exploitation is possible.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Network</p></div><div style='flex: 1;margin-left:5px;'><p>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).</p></div></div><div class='tw-h5' style='padding-left:10px'>Attack Complexity</div><p style='padding-left:10px'>This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Privileges Required</div><p style='padding-left:10px'>This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>None</p></div><div style='flex: 1;margin-left:5px;'><p>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.</p></div></div><div class='tw-h5' style='padding-left:10px'>User Interaction</div><p style='padding-left:10px'>This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Required</p></div><div style='flex: 1;margin-left:5px;'><p>Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Base: Scope Metrics</h4><p>The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.</p><div class='tw-h5' style='padding-left:10px'>Scope</div><p style='padding-left:10px'>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.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Changed</p></div><div style='flex: 1;margin-left:5px;'><p>An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Base: Impact Metrics</h4><p>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.</p><div class='tw-h5' style='padding-left:10px'>Confidentiality Impact</div><p style='padding-left:10px'>This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Integrity Impact</div><p style='padding-left:10px'>This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>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.</p></div></div><div class='tw-h5' style='padding-left:10px'>Availability Impact</div><p style='padding-left:10px'>This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p style='text-align: center;background-color: black;color:white;'>None</p></div><div style='flex: 1;margin-left:5px;'><p>There is no impact to availability within the impacted component.</p></div></div><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Temporal Metrics</h4><p>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.</p><h4 style='background-color: white; border: 1px solid gray; padding: 5px;'>Environmental Metrics</h4><p>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.</p>                        </div>
                    </div>
                </div>
            </div>
        </div>
                        </td>
                        <td>nvd@nist.gov</td>
                    </tr>
                </tbody>
            </table>
        </div>
            <div class="separator my-10"></div>

<h2>EPSS</h2>
            <div class="mb-4">EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.</div>

<h3>Score EPSS</h3>
            <div>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.</div>
            <div id="chartEpss"></div>

<h3>Percentile EPSS</h3>
            <div>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.</div>
            <div id="chartPercentile"></div>
            <div class="text-center">
                <a href="https://www.first.org/epss/" target="_parent">EPSS First.org<i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a>
            </div>

<div style="text-align:center;">
                <input type="button" class="" value="Voir le tableau des valeurs" onclick="$(document).ready(function() {$('#chartPercentileBoard').slideToggle();});">
            </div>
            <div id="chartPercentileBoard" style="display: none;align-content: center;">
                <br><table border="1" cellspacing="0" cellpadding="5" class="table table-bordered"><thead><tr><th>Date</th><th>Percentile</th></tr></thead><tbody><tr><td>2022-07-17</td><td>3%</td></tr><tr><td>2022-07-24</td><td>38%</td></tr><tr><td>2022-08-14</td><td>39%</td></tr><tr><td>2022-11-13</td><td>4%</td></tr><tr><td>2022-11-20</td><td>39%</td></tr><tr><td>2022-11-27</td><td>4%</td></tr><tr><td>2023-02-26</td><td>41%</td></tr><tr><td>2023-03-12</td><td>3%</td></tr><tr><td>2023-04-02</td><td>5%</td></tr><tr><td>2023-06-18</td><td>54%</td></tr><tr><td>2023-07-09</td><td>55%</td></tr><tr><td>2023-07-23</td><td>69%</td></tr><tr><td>2023-08-20</td><td>66%</td></tr><tr><td>2023-09-03</td><td>67%</td></tr><tr><td>2023-10-22</td><td>69%</td></tr><tr><td>2023-10-29</td><td>7%</td></tr><tr><td>2023-12-03</td><td>69%</td></tr><tr><td>2023-12-10</td><td>7%</td></tr><tr><td>2023-12-31</td><td>72%</td></tr><tr><td>2024-02-11</td><td>76%</td></tr><tr><td>2024-06-02</td><td>76%</td></tr><tr><td>2024-07-28</td><td>76%</td></tr><tr><td>2024-08-11</td><td>77%</td></tr><tr><td>2024-12-22</td><td>76%</td></tr><tr><td>2025-01-19</td><td>76%</td></tr><tr><td>2025-03-18</td><td>71%</td></tr><tr><td>2025-03-30</td><td>71%</td></tr><tr><td>2025-04-06</td><td>72%</td></tr><tr><td>2025-04-09</td><td>75%</td></tr><tr><td>2025-04-30</td><td>71%</td></tr><tr><td>2025-05-01</td><td>63%</td></tr><tr><td>2025-05-04</td><td>71%</td></tr><tr><td>2025-06-01</td><td>63%</td></tr><tr><td>2025-06-04</td><td>71%</td></tr><tr><td>2025-07-01</td><td>63%</td></tr><tr><td>2025-07-04</td><td>72%</td></tr><tr><td>2025-07-16</td><td>73%</td></tr><tr><td>2025-07-28</td><td>9%</td></tr><tr><td>2025-07-30</td><td>91%</td></tr><tr><td>2025-08-01</td><td>8%</td></tr><tr><td>2025-08-02</td><td>81%</td></tr><tr><td>2025-08-02</td><td>81%</td></tr></tbody></table>            </div>

};
            </script>

<h2 class="tw-h3">Products Mentioned</h2>

<h3 class='tw-h4'>Configuraton 0</h3><p>Angularjs>>Angular >> Version *<ul><li style='margin-left:20px;'>Angularjs>>Angular >> Version -<a href='/fr/cpe/13BE11F7-4BA6-4592-80C6-779A7EC2F3E3.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.0<a href='/fr/cpe/867C9CBA-6FD2-4F74-B271-2CEA55EB192A.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.1<a href='/fr/cpe/D4E1BB0A-F3DD-4E48-9663-6CF4C6000706.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.2<a href='/fr/cpe/AC92B9B9-EAAC-4217-AEED-A119EFF618A0.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.3<a href='/fr/cpe/BF1D5CED-FAE7-4FB5-91E6-C13A02BA4699.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.4<a href='/fr/cpe/DF242E09-49A2-4A26-BE9F-FE534E6B2459.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.5<a href='/fr/cpe/5463080A-6F21-4A3B-9291-2C346E225A54.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.6<a href='/fr/cpe/52A122BD-00B1-47F3-805F-8A0E6B8C82E8.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.7<a href='/fr/cpe/44B98ED1-DA00-47FB-8181-E61D3481F60B.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.8<a href='/fr/cpe/BCB09953-4082-4107-8B34-3A5CFD8BA151.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.7.9<a href='/fr/cpe/53CBBE96-C06F-4CE8-AEB7-3659B18E2025.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.8.0<a href='/fr/cpe/29903164-B126-42C7-9433-79876C2BDE9C.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.8.1<a href='/fr/cpe/8BD91415-4B44-44DB-AFCC-7C6F69FD16C7.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.8.2<a href='/fr/cpe/838491FB-157B-4550-9385-DB12368010B5.html'> (Open CPE detail)</a></li><li style='margin-left:20px;'>Angularjs>>Angular >> Version 1.8.3<a href='/fr/cpe/C7B823EF-FD97-4DE6-95E8-74AAE0AA3F21.html'> (Open CPE detail)</a></li></ul></p>            <div class="separator my-10"></div>

<h2 class='tw-h3'>Références</h2><div style='margin-bottom: 10px;'><a href='https://security.snyk.io/vuln/SNYK-JS-ANGULAR-2949781' target='_blank'>https://security.snyk.io/vuln/SNYK-JS-ANGULAR-2949781 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2949782' target='_blank'>https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2949782 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2949783' target='_blank'>https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2949783 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBANGULAR-2949784' target='_blank'>https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBANGULAR-2949784 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://security.snyk.io/vuln/SNYK-DOTNET-ANGULARJSCORE-6084031' target='_blank'>https://security.snyk.io/vuln/SNYK-DOTNET-ANGULARJSCORE-6084031 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://security.snyk.io/vuln/SNYK-DOTNET-ANGULARJS-10771617' target='_blank'>https://security.snyk.io/vuln/SNYK-DOTNET-ANGULARJS-10771617 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://neverendingsupport.github.io/angularjs-poc-cve-2022-25869' target='_blank'>https://neverendingsupport.github.io/angularjs-poc-cve-2022-25869 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://glitch.com/edit/%23%21/angular-repro-textarea-xss' target='_blank'>https://glitch.com/edit/%23%21/angular-repro-textarea-xss <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br><span style='margin-left:20px;'>Tags : Broken Link</span></div><div style='margin-bottom: 10px;'><a href='https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2949783' target='_blank'>https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2949783 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br><span style='margin-left:20px;'>Tags : Exploit, Third Party Advisory</span></div><div style='margin-bottom: 10px;'><a href='https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBANGULAR-2949784' target='_blank'>https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBANGULAR-2949784 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br><span style='margin-left:20px;'>Tags : Exploit, Third Party Advisory</span></div><div style='margin-bottom: 10px;'><a href='https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2949782' target='_blank'>https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2949782 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br><span style='margin-left:20px;'>Tags : Exploit, Third Party Advisory</span></div><div style='margin-bottom: 10px;'><a href='https://snyk.io/vuln/SNYK-JS-ANGULAR-2949781' target='_blank'>https://snyk.io/vuln/SNYK-JS-ANGULAR-2949781 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br><span style='margin-left:20px;'>Tags : Exploit, Third Party Advisory</span></div><div class="separator my-10"></div>                            </div>
                        </div>

</div>
                </div>
            </div>
        </div>
                <script type="application/ld+json">
        {
            "@context": "https://schema.org",
          "@type": "NewsArticle",
          "headline": "Information about the CVE-2022-25869 vulnerability.",
          "datePublished": "2022-07-15T20:02:02+00:00",
          "dateModified": "2025-07-28T09:59:04+00:00",
          "author": [{
            "@type": "Organization",
              "name": "The MITRE Corporation",
              "url": "https://www.cve.org"
            },{
              "@type": "Organization",
              "name": "CVE Find",
              "url": "https://www.cvefind.com"
          }]
        }
        </script>
        
 
                    
                            <div class="footer py-4 d-flex flex-lg-column" id="kt_footer">
            <div class="container-xxl d-flex flex-column flex-md-row align-items-center justify-content-between">
                <div class="text-gray-900 order-2 order-md-1">
                    <span class="text-muted fw-semibold me-1">2025©</span>
                    <a href="https://www.tesweb.com" target="_blank" class="text-gray-800 text-hover-primary">tesweb SA</a>,
                    <a href="https://www.bexxo.ch" target="_blank" class="text-gray-800 text-hover-primary">bexxo Cyber Security</a>
                </div>
                <ul class="menu menu-gray-600 menu-hover-primary fw-semibold order-1">

<li class="menu-item">
                        <a href="/fr/official.html" class="menu-link px-2">Database Partners</a>
                    </li>
                    <li class="menu-item">
                        <a href="/fr/gdpr.html" class="menu-link px-2">GDPR</a>
                    </li>
                    <li class="menu-item">
                        <a href="/fr/contact.html" class="menu-link px-2">Contact</a>
                    </li>
                    <li class="menu-item">
                        <a href="/fr/plan-price.html" class="menu-link px-2">Purchase</a>
                    </li>
                    <li class="menu-item">
                        <a href="https://www.linkedin.com/company/cve-find/" class="menu-link px-2" target="_blank"><img src="/media/social/linkedin.svg" width="40" height="40" alt="LinkedIn Account"/></a>
                    </li>
                    <li class="menu-item">
                        <a href="https://www.facebook.com/people/CVE-Find-Alert/61561116452093/" class="menu-link px-2" target="_blank"><img src="/media/social/facebook.svg" width="40" height="40" alt="Facebook Account"/></a>
                    </li>
                    <li class="menu-item">
                        <a href="https://x.com/cvefindcom" class="menu-link px-2" target="_blank"><img src="/media/social/twitter.svg" width="40" height="40" alt="Twitter Account"/></a>
                    </li>
                </ul>
            </div>
        </div>
        <div class="footer py-4">
            <div class="container-xxl align-items-center justify-content-between">
                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 <a href="https://cve.mitre.org/" target="_blank">MITRE Corporation</a> et la <a href="https://nvd.nist.gov/" target="_blank">National Vulnerability Database (NVD)</a>. Le catalogue des vulnérabilités activement exploitées (KEV) provient de la <a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" target="_blank">Cybersecurity and Infrastructure Security Agency (CISA)</a>, tandis que les scores EPSS sont issus de <a href="https://www.first.org/epss/" target="_blank">FIRST.org</a>. Enfin, les données relatives aux faiblesses logicielles (CWE) et aux schémas d'attaque courants (CAPEC)
                sont maintenues par <a href="https://mitre.org/" target="_blank">MITRE Corporation</a>, et les informations sur les configurations
                logicielles et matérielles (CPE) proviennent du <a href="https://nvd.nist.gov/products/cpe" target="_blank">NVD</a>.            </div>
        </div>

</div>
            </div>
        </div>

<script>var hostUrl = "assets/";</script>
                
                <script src="/plugins/global/plugins.bundle.js"></script>
                <script src="/js/scripts.bundle.js"></script>

<script src='https://www.cvefind.com/plugins/custom/datatables/datatables.bundle.js'></script>
<script src='https://www.cvefind.com/js/app/bloc/cve/epss.min.js'></script>
<script src='https://www.cvefind.com/js/aceeditor/ace.js'></script>
<script src='https://www.cvefind.com/js/app/bloc/cve/exploitdb.min.js'></script>

</body>
        </html>

CVE-2022-25869 : Détail

CVE-2022-25869

Descriptions du CVE