cve-2022-24999
Vulnerability from cvelistv5
Published
2022-11-26 00:00
Modified
2024-08-03 04:29
Severity ?
EPSS score ?
1.71% (0.8114)
Summary
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).
References
cve@mitre.orghttps://github.com/expressjs/express/releases/tag/4.17.3Release Notes
cve@mitre.orghttps://github.com/ljharb/qs/pull/428Issue Tracking, Patch
cve@mitre.orghttps://github.com/n8tz/CVE-2022-24999Exploit, Third Party Advisory
cve@mitre.orghttps://lists.debian.org/debian-lts-announce/2023/01/msg00039.htmlMailing List, Third Party Advisory
cve@mitre.orghttps://security.netapp.com/advisory/ntap-20230908-0005/
af854a3a-2127-422b-91ae-364da2661108https://github.com/expressjs/express/releases/tag/4.17.3Release Notes
af854a3a-2127-422b-91ae-364da2661108https://github.com/ljharb/qs/pull/428Issue Tracking, Patch
af854a3a-2127-422b-91ae-364da2661108https://github.com/n8tz/CVE-2022-24999Exploit, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://lists.debian.org/debian-lts-announce/2023/01/msg00039.htmlMailing List, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://security.netapp.com/advisory/ntap-20230908-0005/
Impacted products
Vendor Product Version
n/a n/a Version: n/a
Show details on NVD website

To clipboard 

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-03T04:29:01.569Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://github.com/expressjs/express/releases/tag/4.17.3",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://github.com/ljharb/qs/pull/428",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://github.com/n8tz/CVE-2022-24999",
               },
               {
                  name: "[debian-lts-announce] 20230130 [SECURITY] [DLA 3299-1] node-qs security update",
                  tags: [
                     "mailing-list",
                     "x_transferred",
                  ],
                  url: "https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://security.netapp.com/advisory/ntap-20230908-0005/",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "n/a",
               vendor: "n/a",
               versions: [
                  {
                     status: "affected",
                     version: "n/a",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "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).",
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     description: "n/a",
                     lang: "en",
                     type: "text",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2023-09-08T16:06:42.462757",
            orgId: "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
            shortName: "mitre",
         },
         references: [
            {
               url: "https://github.com/expressjs/express/releases/tag/4.17.3",
            },
            {
               url: "https://github.com/ljharb/qs/pull/428",
            },
            {
               url: "https://github.com/n8tz/CVE-2022-24999",
            },
            {
               name: "[debian-lts-announce] 20230130 [SECURITY] [DLA 3299-1] node-qs security update",
               tags: [
                  "mailing-list",
               ],
               url: "https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html",
            },
            {
               url: "https://security.netapp.com/advisory/ntap-20230908-0005/",
            },
         ],
      },
   },
   cveMetadata: {
      assignerOrgId: "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
      assignerShortName: "mitre",
      cveId: "CVE-2022-24999",
      datePublished: "2022-11-26T00:00:00",
      dateReserved: "2022-02-14T00:00:00",
      dateUpdated: "2024-08-03T04:29:01.569Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      fkie_nvd: {
         configurations: "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\", \"versionEndExcluding\": \"6.2.4\", \"matchCriteriaId\": \"F7960844-79EB-454C-BD4C-C79387E2E573\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\", \"versionStartIncluding\": \"6.3.0\", \"versionEndExcluding\": \"6.3.3\", \"matchCriteriaId\": \"B836471B-BF39-4B52-B837-70B494D2C45F\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\", \"versionStartIncluding\": \"6.5.0\", \"versionEndExcluding\": \"6.5.3\", \"matchCriteriaId\": \"DF319EA6-E68F-41A8-BB21-FE30F6BD1A9C\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\", \"versionStartIncluding\": \"6.7.0\", \"versionEndExcluding\": \"6.7.3\", \"matchCriteriaId\": \"E43C2419-E3F8-4123-8FA8-A0C1B4244D77\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\", \"versionStartIncluding\": \"6.8.0\", \"versionEndExcluding\": \"6.8.3\", \"matchCriteriaId\": \"BB20DBEF-67E2-49FB-BB55-C86F7A83028F\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\", \"versionStartIncluding\": \"6.9.0\", \"versionEndExcluding\": \"6.9.7\", \"matchCriteriaId\": \"49C25B47-56FD-43BF-9DA4-A6100DD291EE\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\", \"versionStartIncluding\": \"6.10.0\", \"versionEndExcluding\": \"6.10.3\", \"matchCriteriaId\": \"750DDAB9-4454-4087-8DA1-D05280F59081\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:qs_project:qs:6.4.0:*:*:*:*:node.js:*:*\", \"matchCriteriaId\": \"535F43BA-C0A4-441A-A13C-A221ED855613\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:qs_project:qs:6.6.0:*:*:*:*:node.js:*:*\", \"matchCriteriaId\": \"870A2680-00C2-43D2-9C4B-D8F52DB16AA1\"}]}]}, {\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:*:*:*:*:*:node.js:*:*\", \"versionEndExcluding\": \"4.17.3\", \"matchCriteriaId\": \"31382A93-AA97-4D14-ACF6-129F1BDDFD6D\"}]}]}, {\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"07B237A9-69A3-4A9C-9DA0-4E06BD37AE73\"}]}]}]",
         descriptions: "[{\"lang\": \"en\", \"value\": \"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).\"}, {\"lang\": \"es\", \"value\": \"qs anterior a 6.10.3, como se usa en Express anterior a 4.17.3 y otros productos, permite a los atacantes provocar que un proceso de Nodo se cuelgue para una aplicaci\\u00f3n Express porque se puede usar una clave __ proto__. En muchos casos de uso t\\u00edpicos de Express, un atacante remoto no autenticado puede colocar el payload del ataque en la cadena de consulta de la URL que se utiliza para visitar la aplicaci\\u00f3n, como a[__proto__]=b&a[__proto__]&a[length] =100000000. La soluci\\u00f3n se respald\\u00f3 a qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3 y 6.2.4 (y por lo tanto a Express 4.17.3, que tiene \\\"deps : qs@6.9.7\\\" en la descripci\\u00f3n de su versi\\u00f3n, no es vulnerable).\"}]",
         id: "CVE-2022-24999",
         lastModified: "2024-11-21T06:51:31.643",
         metrics: "{\"cvssMetricV31\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\", \"baseScore\": 7.5, \"baseSeverity\": \"HIGH\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"NONE\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 3.9, \"impactScore\": 3.6}]}",
         published: "2022-11-26T22:15:10.153",
         references: "[{\"url\": \"https://github.com/expressjs/express/releases/tag/4.17.3\", \"source\": \"cve@mitre.org\", \"tags\": [\"Release Notes\"]}, {\"url\": \"https://github.com/ljharb/qs/pull/428\", \"source\": \"cve@mitre.org\", \"tags\": [\"Issue Tracking\", \"Patch\"]}, {\"url\": \"https://github.com/n8tz/CVE-2022-24999\", \"source\": \"cve@mitre.org\", \"tags\": [\"Exploit\", \"Third Party Advisory\"]}, {\"url\": \"https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html\", \"source\": \"cve@mitre.org\", \"tags\": [\"Mailing List\", \"Third Party Advisory\"]}, {\"url\": \"https://security.netapp.com/advisory/ntap-20230908-0005/\", \"source\": \"cve@mitre.org\"}, {\"url\": \"https://github.com/expressjs/express/releases/tag/4.17.3\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Release Notes\"]}, {\"url\": \"https://github.com/ljharb/qs/pull/428\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Issue Tracking\", \"Patch\"]}, {\"url\": \"https://github.com/n8tz/CVE-2022-24999\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Exploit\", \"Third Party Advisory\"]}, {\"url\": \"https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Mailing List\", \"Third Party Advisory\"]}, {\"url\": \"https://security.netapp.com/advisory/ntap-20230908-0005/\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
         sourceIdentifier: "cve@mitre.org",
         vulnStatus: "Modified",
         weaknesses: "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-1321\"}]}]",
      },
      nvd: "{\"cve\":{\"id\":\"CVE-2022-24999\",\"sourceIdentifier\":\"cve@mitre.org\",\"published\":\"2022-11-26T22:15:10.153\",\"lastModified\":\"2024-11-21T06:51:31.643\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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).\"},{\"lang\":\"es\",\"value\":\"qs anterior a 6.10.3, como se usa en Express anterior a 4.17.3 y otros productos, permite a los atacantes provocar que un proceso de Nodo se cuelgue para una aplicación Express porque se puede usar una clave __ proto__. En muchos casos de uso típicos de Express, un atacante remoto no autenticado puede colocar el payload del ataque en la cadena de consulta de la URL que se utiliza para visitar la aplicación, como a[__proto__]=b&a[__proto__]&a[length] =100000000. La solución se respaldó a qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3 y 6.2.4 (y por lo tanto a Express 4.17.3, que tiene \\\"deps : qs@6.9.7\\\" en la descripción de su versión, no es vulnerable).\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-1321\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\",\"versionEndExcluding\":\"6.2.4\",\"matchCriteriaId\":\"F7960844-79EB-454C-BD4C-C79387E2E573\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\",\"versionStartIncluding\":\"6.3.0\",\"versionEndExcluding\":\"6.3.3\",\"matchCriteriaId\":\"B836471B-BF39-4B52-B837-70B494D2C45F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\",\"versionStartIncluding\":\"6.5.0\",\"versionEndExcluding\":\"6.5.3\",\"matchCriteriaId\":\"DF319EA6-E68F-41A8-BB21-FE30F6BD1A9C\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\",\"versionStartIncluding\":\"6.7.0\",\"versionEndExcluding\":\"6.7.3\",\"matchCriteriaId\":\"E43C2419-E3F8-4123-8FA8-A0C1B4244D77\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\",\"versionStartIncluding\":\"6.8.0\",\"versionEndExcluding\":\"6.8.3\",\"matchCriteriaId\":\"BB20DBEF-67E2-49FB-BB55-C86F7A83028F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\",\"versionStartIncluding\":\"6.9.0\",\"versionEndExcluding\":\"6.9.7\",\"matchCriteriaId\":\"49C25B47-56FD-43BF-9DA4-A6100DD291EE\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*\",\"versionStartIncluding\":\"6.10.0\",\"versionEndExcluding\":\"6.10.3\",\"matchCriteriaId\":\"750DDAB9-4454-4087-8DA1-D05280F59081\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:qs_project:qs:6.4.0:*:*:*:*:node.js:*:*\",\"matchCriteriaId\":\"535F43BA-C0A4-441A-A13C-A221ED855613\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:qs_project:qs:6.6.0:*:*:*:*:node.js:*:*\",\"matchCriteriaId\":\"870A2680-00C2-43D2-9C4B-D8F52DB16AA1\"}]}]},{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:*:*:*:*:*:node.js:*:*\",\"versionEndExcluding\":\"4.17.3\",\"matchCriteriaId\":\"31382A93-AA97-4D14-ACF6-129F1BDDFD6D\"}]}]},{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"07B237A9-69A3-4A9C-9DA0-4E06BD37AE73\"}]}]}],\"references\":[{\"url\":\"https://github.com/expressjs/express/releases/tag/4.17.3\",\"source\":\"cve@mitre.org\",\"tags\":[\"Release Notes\"]},{\"url\":\"https://github.com/ljharb/qs/pull/428\",\"source\":\"cve@mitre.org\",\"tags\":[\"Issue Tracking\",\"Patch\"]},{\"url\":\"https://github.com/n8tz/CVE-2022-24999\",\"source\":\"cve@mitre.org\",\"tags\":[\"Exploit\",\"Third Party Advisory\"]},{\"url\":\"https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html\",\"source\":\"cve@mitre.org\",\"tags\":[\"Mailing List\",\"Third Party Advisory\"]},{\"url\":\"https://security.netapp.com/advisory/ntap-20230908-0005/\",\"source\":\"cve@mitre.org\"},{\"url\":\"https://github.com/expressjs/express/releases/tag/4.17.3\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Release Notes\"]},{\"url\":\"https://github.com/ljharb/qs/pull/428\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Issue Tracking\",\"Patch\"]},{\"url\":\"https://github.com/n8tz/CVE-2022-24999\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Exploit\",\"Third Party Advisory\"]},{\"url\":\"https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\",\"Third Party Advisory\"]},{\"url\":\"https://security.netapp.com/advisory/ntap-20230908-0005/\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.