BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-24999High confidence

qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used

Unknown · Unknown

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 29 Apr 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 15.62% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-qsVendor fix publishedDebian records a fixed source-package version for this release.6.10.3+ds+~6.9.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcenode-qsVendor fix publishedDebian records a fixed source-package version for this release.6.10.3+ds+~6.9.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcenode-qsVendor fix publishedDebian records a fixed source-package version for this release.6.10.3+ds+~6.9.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcenode-qsVendor fix publishedDebian records a fixed source-package version for this release.6.10.3+ds+~6.9.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Open-source package ranges9 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmqs>= 6.10.0, < 6.10.36.10.3GitHub advisory ↗github reviewed aggregator · 29 Apr 2025
npmqs>= 6.9.0, < 6.9.76.9.7GitHub advisory ↗github reviewed aggregator · 29 Apr 2025
npmqs>= 6.8.0, < 6.8.36.8.3GitHub advisory ↗github reviewed aggregator · 29 Apr 2025
npmqs>= 6.7.0, < 6.7.36.7.3GitHub advisory ↗github reviewed aggregator · 29 Apr 2025
npmqs>= 6.6.0, < 6.6.16.6.1GitHub advisory ↗github reviewed aggregator · 29 Apr 2025
npmqs>= 6.5.0, < 6.5.36.5.3GitHub advisory ↗github reviewed aggregator · 29 Apr 2025
npmqs>= 6.4.0, < 6.4.16.4.1GitHub advisory ↗github reviewed aggregator · 29 Apr 2025
npmqs>= 6.3.0, < 6.3.36.3.3GitHub advisory ↗github reviewed aggregator · 29 Apr 2025
npmqs< 6.2.46.2.4GitHub advisory ↗github reviewed aggregator · 29 Apr 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2022-24999 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityexpress: "qs" prototype poisoning causes the hang of the node process
60 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • rh-dotnet31-aspnetcore-runtime-3.1 as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-aspnetcore-targeting-pack-3.1 as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet-apphost-pack-3.1 as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet-host as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet-hostfxr-3.1 as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet-runtime-3.1 as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet-sdk-3.1 as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet-sdk-3.1-source-built-artifacts as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet-targeting-pack-3.1 as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet-templates-3.1 as a component of .NET Core 3.1 on Red Hat Enterprise Linux
  • rh-dotnet31-dotnet.src as a component of .NET Core 3.1 on Red Hat Enterprise Linux
Summary
A flaw was found in the express.js npm package of nodejs:14 module stream. Express.js Express is vulnerable to a denial of service caused by a prototype pollution flaw in qs. By adding or modifying properties of Object.prototype using a __proto__ or constructor payload, a remote attacker can cause a denial of service.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
9AKK108470A8565 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2022-24999
2 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • RMC-100 (2105457-036 to 2105457-044)
  • RMC-100 LITE (2106229-010 to 2106229-016)
Summary
A vulnerability exists in the web UI (REST interface) included in the product versions listed above. An attacker could exploit the vulnerability by sending a specially crafted message to the web UI node, causing a Node process hang, requiring restart of the REST interface (disable/enable).
Remediation
The problem is corrected in the following product versions: RMC-100 Customer Package (2105452-048). RMC-100 LITE Customer Package (2106260-017). ABB recommends that customers apply the update at earliest convenience. Please find these updates here: RMC - Flow Computers (Flow Computers, Remote Controllers and RTUs) | Flow Computers | ABB
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-7366

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).

What

qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-1321 ↗

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-1321Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-2229Splunk Splunk Enterprise: Mehrere Schwachstellen

Ein entfernter, authentifizierter Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise ausnutzen, um beliebigen Code auszuführen, einen 'Denial of Service'-Zustand zu verursachen, seine Privilegien zu erweitern und weitere, nicht spezifizierte Auswirkungen zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2023-1295Red Hat OpenShift: Mehrere Schwachstellen

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2023-0809IBM QRadar SIEM: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, Informationen offenzulegen, Informationen falsch darzustellen, einen Denial of Service Zustand herbeizuführen, Sicherheitsvorkehrungen zu umgehen, einen Cross-Site-Scripting-Angriff durchzuführen oder unbekannte Auswirkungen zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2023-1350Splunk Splunk Enterprise: Mehrere Schwachstellen in Komponenten von Drittanbietern

Ein Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise in diversen Komponenten von Drittanbietern ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-0822HCL BigFix: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in HCL BigFix ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-0398Red Hat Advanced Cluster Management for Kubernetes: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle im Red Hat Advanced Cluster Management for Kubernetes ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20221130Security Bulletin 30 Nov 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 30 Nov 2022, published on 30 November 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

Bulletin de sécurité IBM 7289777 du 28 septembre 2026 https://www.ibm.com/support/pages/node/7289777 Bulletin de sécurité IBM 7289781 du 28 septembre 2026 https://www.ibm.com/support/pages/node/7289781 Bulletin de sécurité IBM 7289828 du 28 septembre 2026 https://www.ibm.com/support/pages/node/7289828 Bulletin de sécurité IBM 7290182 du 30 septembre 2026 https://www.ibm.com/support/pages/node/7290182 Référence CVE CVE-2018-16487 https://www.cve.org/CVERecord?id=CVE-2018-16487 Référence CVE CVE-2020-15366 https://www.cve.org/CVERecord?id=CVE-2020-15366 Référence CVE CVE-2021-23337 https://www.cve.org/CVERecord?id=CVE-2021-23337 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-3517 https://www.cve.org/CVERecord?id=CVE-2022-3517 Référence CVE CVE-2024-55565 https://www.cve.org/CVERecord?id=CVE-2024-55565 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-27152 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0627Multiples vulnérabilités dans les produits IBM

sécurité IBM 7240267 du 22 juillet 2025 https://www.ibm.com/support/pages/node/7240267 Bulletin de sécurité IBM 7240466 du 23 juillet 2025 https://www.ibm.com/support/pages/node/7240466 Bulletin de sécurité IBM 7240471 du 23 juillet 2025 https://www.ibm.com/support/pages/node/7240471 Bulletin de sécurité IBM 7240474 du 23 juillet 2025 https://www.ibm.com/support/pages/node/7240474 Bulletin de sécurité IBM 7240530 du 24 juillet 2025 https://www.ibm.com/support/pages/node/7240530 Référence CVE CVE-2021-3121 https://www.cve.org/CVERecord?id=CVE-2021-3121 Référence CVE CVE-2021-38561 https://www.cve.org/CVERecord?id=CVE-2021-38561 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-25883 https://www.cve.org/CVERecord?id=CVE-2022-25883 Référence CVE CVE-2023-26115 https://www.cve.org/CVERecord?id=CVE-2023-26115 Référence CVE CVE-2023-26136 https://www.cve.org/CVERecord?id=CVE-2023-26136 Référence CVE CVE-2023-32305 https://www.cve.org/CVERecord?id=CVE-2023-32305 Référence CVE CVE-2023-43804 https://www.cve.org/CVERecord?id=CVE-2023-43804 Référence CVE CVE-2023-44270 https://www.cve.org/CVERecord?id=CVE-2023-44270 Référence CVE CVE-2023-45133 https://www.cve.org/CVERecord?id=CVE-2023-45133 Référence CVE CVE-2023-46298 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0170Multiples vulnérabilités dans les produits IBM

ERecord?id=CVE-2018-20190 Référence CVE CVE-2018-20821 https://www.cve.org/CVERecord?id=CVE-2018-20821 Référence CVE CVE-2018-25032 https://www.cve.org/CVERecord?id=CVE-2018-25032 Référence CVE CVE-2019-6283 https://www.cve.org/CVERecord?id=CVE-2019-6283 Référence CVE CVE-2019-6286 https://www.cve.org/CVERecord?id=CVE-2019-6286 Référence CVE CVE-2020-7598 https://www.cve.org/CVERecord?id=CVE-2020-7598 Référence CVE CVE-2021-27290 https://www.cve.org/CVERecord?id=CVE-2021-27290 Référence CVE CVE-2021-35065 https://www.cve.org/CVERecord?id=CVE-2021-35065 Référence CVE CVE-2021-44906 https://www.cve.org/CVERecord?id=CVE-2021-44906 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-25881 https://www.cve.org/CVERecord?id=CVE-2022-25881 Référence CVE CVE-2022-37434 https://www.cve.org/CVERecord?id=CVE-2022-37434 Référence CVE CVE-2022-48554 https://www.cve.org/CVERecord?id=CVE-2022-48554 Référence CVE CVE-2022-4904 https://www.cve.org/CVERecord?id=CVE-2022-4904 Référence CVE CVE-2023-23918 https://www.cve.org/CVERecord?id=CVE-2023-23918 Référence CVE CVE-2023-23919 https://www.cve.org/CVERecord?id=CVE-2023-23919 Référence CVE CVE-2023-23920 https://www.cve.org/CVERecord?id=CVE-2023-23920 Référence CVE CVE-2023-23936 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0958Multiples vulnérabilités dans les produits IBM

d?id=CVE-2021-47461 Référence CVE CVE-2021-47468 https://www.cve.org/CVERecord?id=CVE-2021-47468 Référence CVE CVE-2021-47491 https://www.cve.org/CVERecord?id=CVE-2021-47491 Référence CVE CVE-2021-47548 https://www.cve.org/CVERecord?id=CVE-2021-47548 Référence CVE CVE-2021-47579 https://www.cve.org/CVERecord?id=CVE-2021-47579 Référence CVE CVE-2021-47624 https://www.cve.org/CVERecord?id=CVE-2021-47624 Référence CVE CVE-2022-23181 https://www.cve.org/CVERecord?id=CVE-2022-23181 Référence CVE CVE-2022-23471 https://www.cve.org/CVERecord?id=CVE-2022-23471 Référence CVE CVE-2022-23648 https://www.cve.org/CVERecord?id=CVE-2022-23648 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-25762 https://www.cve.org/CVERecord?id=CVE-2022-25762 Référence CVE CVE-2022-29885 https://www.cve.org/CVERecord?id=CVE-2022-29885 Référence CVE CVE-2022-31030 https://www.cve.org/CVERecord?id=CVE-2022-31030 Référence CVE CVE-2022-34305 https://www.cve.org/CVERecord?id=CVE-2022-34305 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-42252 https://www.cve.org/CVERecord?id=CVE-2022-42252 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=CVE-2022-48632 Référence CVE CVE-2022-48743 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0873Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0145Multiples vulnérabilités dans les produits IBM

d?id=CVE-2022-23529 Référence CVE CVE-2022-23539 https://www.cve.org/CVERecord?id=CVE-2022-23539 Référence CVE CVE-2022-23540 https://www.cve.org/CVERecord?id=CVE-2022-23540 Référence CVE CVE-2022-23541 https://www.cve.org/CVERecord?id=CVE-2022-23541 Référence CVE CVE-2022-23772 https://www.cve.org/CVERecord?id=CVE-2022-23772 Référence CVE CVE-2022-23773 https://www.cve.org/CVERecord?id=CVE-2022-23773 Référence CVE CVE-2022-23806 https://www.cve.org/CVERecord?id=CVE-2022-23806 Référence CVE CVE-2022-24675 https://www.cve.org/CVERecord?id=CVE-2022-24675 Référence CVE CVE-2022-24921 https://www.cve.org/CVERecord?id=CVE-2022-24921 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-25881 https://www.cve.org/CVERecord?id=CVE-2022-25881 Référence CVE CVE-2022-25883 https://www.cve.org/CVERecord?id=CVE-2022-25883 Référence CVE CVE-2022-27664 https://www.cve.org/CVERecord?id=CVE-2022-27664 Référence CVE CVE-2022-27776 https://www.cve.org/CVERecord?id=CVE-2022-27776 Référence CVE CVE-2022-27781 https://www.cve.org/CVERecord?id=CVE-2022-27781 Référence CVE CVE-2022-27782 https://www.cve.org/CVERecord?id=CVE-2022-27782 Référence CVE CVE-2022-28131 https://www.cve.org/CVERecord?id=CVE-2022-28131 Référence CVE CVE-2022-28327 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0701Multiples vulnérabilités dans Splunk

cord?id=CVE-2022-1962 Référence CVE CVE-2022-22576 https://www.cve.org/CVERecord?id=CVE-2022-22576 Référence CVE CVE-2022-2309 https://www.cve.org/CVERecord?id=CVE-2022-2309 Référence CVE CVE-2022-23491 https://www.cve.org/CVERecord?id=CVE-2022-23491 Référence CVE CVE-2022-23772 https://www.cve.org/CVERecord?id=CVE-2022-23772 Référence CVE CVE-2022-23773 https://www.cve.org/CVERecord?id=CVE-2022-23773 Référence CVE CVE-2022-23806 https://www.cve.org/CVERecord?id=CVE-2022-23806 Référence CVE CVE-2022-24675 https://www.cve.org/CVERecord?id=CVE-2022-24675 Référence CVE CVE-2022-24921 https://www.cve.org/CVERecord?id=CVE-2022-24921 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-25881 https://www.cve.org/CVERecord?id=CVE-2022-25881 Référence CVE CVE-2022-27191 https://www.cve.org/CVERecord?id=CVE-2022-27191 Référence CVE CVE-2022-27536 https://www.cve.org/CVERecord?id=CVE-2022-27536 Référence CVE CVE-2022-27664 https://www.cve.org/CVERecord?id=CVE-2022-27664 Référence CVE CVE-2022-27774 https://www.cve.org/CVERecord?id=CVE-2022-27774 Référence CVE CVE-2022-27775 https://www.cve.org/CVERecord?id=CVE-2022-27775 Référence CVE CVE-2022-27776 https://www.cve.org/CVERecord?id=CVE-2022-27776 Référence CVE CVE-2022-27778 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0574Multiples vulnérabilités dans les produits IBM

.org/CVERecord?id=CVE-2019-4719 Référence CVE CVE-2019-4762 https://www.cve.org/CVERecord?id=CVE-2019-4762 Référence CVE CVE-2020-4310 https://www.cve.org/CVERecord?id=CVE-2020-4310 Référence CVE CVE-2020-4320 https://www.cve.org/CVERecord?id=CVE-2020-4320 Référence CVE CVE-2020-4338 https://www.cve.org/CVERecord?id=CVE-2020-4338 Référence CVE CVE-2020-4682 https://www.cve.org/CVERecord?id=CVE-2020-4682 Référence CVE CVE-2021-38949 https://www.cve.org/CVERecord?id=CVE-2021-38949 Référence CVE CVE-2021-39034 https://www.cve.org/CVERecord?id=CVE-2021-39034 Référence CVE CVE-2022-1471 https://www.cve.org/CVERecord?id=CVE-2022-1471 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-3094 https://www.cve.org/CVERecord?id=CVE-2022-3094 Référence CVE CVE-2022-3736 https://www.cve.org/CVERecord?id=CVE-2022-3736 Référence CVE CVE-2022-3924 https://www.cve.org/CVERecord?id=CVE-2022-3924 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-1370 Référence CVE CVE-2023-21930 https://www.cve.org/CVERecord?id=CVE-2023-21930 Référence CVE CVE-2023-21937 https://www.cve.org/CVERecord?id=CVE-2023-21937 Référence CVE CVE-2023-21938 https://www.cve.org/CVERecord?id=CVE-2023-21938 Référence CVE CVE-2023-21939 https://www.cve.org/CVERecord?id=CVE-2023

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0428Multiples vulnérabilités dans les produits Splunk

cord?id=CVE-2022-1705 Référence CVE CVE-2022-1962 https://www.cve.org/CVERecord?id=CVE-2022-1962 Référence CVE CVE-2022-22576 https://www.cve.org/CVERecord?id=CVE-2022-22576 Référence CVE CVE-2022-23491 https://www.cve.org/CVERecord?id=CVE-2022-23491 Référence CVE CVE-2022-23772 https://www.cve.org/CVERecord?id=CVE-2022-23772 Référence CVE CVE-2022-23773 https://www.cve.org/CVERecord?id=CVE-2022-23773 Référence CVE CVE-2022-23806 https://www.cve.org/CVERecord?id=CVE-2022-23806 Référence CVE CVE-2022-24675 https://www.cve.org/CVERecord?id=CVE-2022-24675 Référence CVE CVE-2022-24921 https://www.cve.org/CVERecord?id=CVE-2022-24921 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-25858 https://www.cve.org/CVERecord?id=CVE-2022-25858 Référence CVE CVE-2022-27191 https://www.cve.org/CVERecord?id=CVE-2022-27191 Référence CVE CVE-2022-27664 https://www.cve.org/CVERecord?id=CVE-2022-27664 Référence CVE CVE-2022-27774 https://www.cve.org/CVERecord?id=CVE-2022-27774 Référence CVE CVE-2022-27775 https://www.cve.org/CVERecord?id=CVE-2022-27775 Référence CVE CVE-2022-27776 https://www.cve.org/CVERecord?id=CVE-2022-27776 Référence CVE CVE-2022-27778 https://www.cve.org/CVERecord?id=CVE-2022-27778 Référence CVE CVE-2022-27779 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0427Multiples vulnérabilités dans les produits IBM

s://www.ibm.com/support/pages/node/6999341 Bulletin de sécurité IBM 6999343 du 30 mai 2023 https://www.ibm.com/support/pages/node/6999343 Bulletin de sécurité IBM 6999619 du 31 mai 2023 https://www.ibm.com/support/pages/node/6999619 Bulletin de sécurité IBM 6999681 du 31 mai 2023 https://www.ibm.com/support/pages/node/6999681 Référence CVE CVE-2018-20801 https://www.cve.org/CVERecord?id=CVE-2018-20801 Référence CVE CVE-2020-10735 https://www.cve.org/CVERecord?id=CVE-2020-10735 Référence CVE CVE-2021-29489 https://www.cve.org/CVERecord?id=CVE-2021-29489 Référence CVE CVE-2022-24736 https://www.cve.org/CVERecord?id=CVE-2022-24736 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-25881 https://www.cve.org/CVERecord?id=CVE-2022-25881 Référence CVE CVE-2022-25901 https://www.cve.org/CVERecord?id=CVE-2022-25901 Référence CVE CVE-2022-31676 https://www.cve.org/CVERecord?id=CVE-2022-31676 Référence CVE CVE-2022-32221 https://www.cve.org/CVERecord?id=CVE-2022-32221 Référence CVE CVE-2022-35977 https://www.cve.org/CVERecord?id=CVE-2022-35977 Référence CVE CVE-2022-3602 https://www.cve.org/CVERecord?id=CVE-2022-3602 Référence CVE CVE-2022-3786 https://www.cve.org/CVERecord?id=CVE-2022-3786 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0276Multiples vulnérabilités dans les produits IBM

d?id=CVE-2022-21724 Référence CVE CVE-2022-22970 https://www.cve.org/CVERecord?id=CVE-2022-22970 Référence CVE CVE-2022-22971 https://www.cve.org/CVERecord?id=CVE-2022-22971 Référence CVE CVE-2022-23437 https://www.cve.org/CVERecord?id=CVE-2022-23437 Référence CVE CVE-2022-23816 https://www.cve.org/CVERecord?id=CVE-2022-23816 Référence CVE CVE-2022-23825 https://www.cve.org/CVERecord?id=CVE-2022-23825 Référence CVE CVE-2022-24785 https://www.cve.org/CVERecord?id=CVE-2022-24785 Référence CVE CVE-2022-24823 https://www.cve.org/CVERecord?id=CVE-2022-24823 Référence CVE CVE-2022-24839 https://www.cve.org/CVERecord?id=CVE-2022-24839 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-25647 https://www.cve.org/CVERecord?id=CVE-2022-25647 Référence CVE CVE-2022-25758 https://www.cve.org/CVERecord?id=CVE-2022-25758 Référence CVE CVE-2022-2588 https://www.cve.org/CVERecord?id=CVE-2022-2588 Référence CVE CVE-2022-25901 https://www.cve.org/CVERecord?id=CVE-2022-25901 Référence CVE CVE-2022-25927 https://www.cve.org/CVERecord?id=CVE-2022-25927 Référence CVE CVE-2022-2625 https://www.cve.org/CVERecord?id=CVE-2022-2625 Référence CVE CVE-2022-26373 https://www.cve.org/CVERecord?id=CVE-2022-26373 Référence CVE CVE-2022-27664 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-021546qs project の qs 他複数ベンダの製品におけるオブジェクトプロトタイプ属性の不適切に制御された変更に関する脆弱性

qs project の qs 他複数ベンダの製品には、オブジェクトプロトタイプ属性の不適切に制御された変更に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 26 Nov 2022 · Last source change 29 Apr 2025, 13:56 UTC · CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-7366
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    n/a · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: search.abb.com/Download.aspx?DocumentID=9AKK108470A8565&LanguageCode=en&DocumentPartId=&Action=Launch; removed remediation: nvd.nist.gov/cve-2022-24999.
    Before
    remediation: nvd.nist.gov/cve-2022-24999
    After
    remediation: search.abb.com/Download.aspx?DocumentID=9AKK108470A8565&LanguageCode=en&DocumentPartId=&Action=Launch
    ABB Product Security Incident Response Team (PSIRT) ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2022-7366↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗Patch or update reference↗CVE authority or vendor reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-24999 · cve.blacktree.nl