GSD-2022-24999
Vulnerability from gsd - Updated: 2023-12-13 01:19Details
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).
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2022-24999",
"id": "GSD-2022-24999",
"references": [
"https://access.redhat.com/errata/RHSA-2023:0050",
"https://advisories.mageia.org/CVE-2022-24999.html",
"https://access.redhat.com/errata/RHSA-2023:0612",
"https://access.redhat.com/errata/RHSA-2023:0794",
"https://access.redhat.com/errata/RHSA-2023:0934",
"https://access.redhat.com/errata/RHSA-2023:0930",
"https://access.redhat.com/errata/RHSA-2023:0932"
]
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"aliases": [
"CVE-2022-24999"
],
"details": "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\u0026a[__proto__]\u0026a[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).",
"id": "GSD-2022-24999",
"modified": "2023-12-13T01:19:42.698390Z",
"schema_version": "1.4.0"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2022-24999",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "n/a",
"version": {
"version_data": [
{
"version_value": "n/a"
}
]
}
}
]
},
"vendor_name": "n/a"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"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\u0026a[__proto__]\u0026a[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)."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "n/a"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/expressjs/express/releases/tag/4.17.3",
"refsource": "CONFIRM",
"url": "https://github.com/expressjs/express/releases/tag/4.17.3"
},
{
"name": "https://github.com/ljharb/qs/pull/428",
"refsource": "CONFIRM",
"url": "https://github.com/ljharb/qs/pull/428"
},
{
"name": "https://github.com/n8tz/CVE-2022-24999",
"refsource": "MISC",
"url": "https://github.com/n8tz/CVE-2022-24999"
},
{
"name": "[debian-lts-announce] 20230130 [SECURITY] [DLA 3299-1] node-qs security update",
"refsource": "MLIST",
"url": "https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html"
},
{
"name": "https://security.netapp.com/advisory/ntap-20230908-0005/",
"refsource": "CONFIRM",
"url": "https://security.netapp.com/advisory/ntap-20230908-0005/"
}
]
}
},
"gitlab.com": {
"advisories": [
{
"affected_range": "\u003c4.17.3",
"affected_versions": "All versions before 4.17.3",
"cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"cwe_ids": [
"CWE-1035",
"CWE-1321",
"CWE-937"
],
"date": "2023-02-16",
"description": "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\u0026a[__proto__]\u0026a[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).",
"fixed_versions": [
"4.17.3"
],
"identifier": "CVE-2022-24999",
"identifiers": [
"CVE-2022-24999"
],
"not_impacted": "All versions starting from 4.17.3",
"package_slug": "npm/express",
"pubdate": "2022-11-26",
"solution": "Upgrade to version 4.17.3 or above.",
"title": "Improperly Controlled Modification of Object Prototype Attributes (\u0027Prototype Pollution\u0027)",
"urls": [
"https://nvd.nist.gov/vuln/detail/CVE-2022-24999",
"https://github.com/n8tz/CVE-2022-24999",
"https://github.com/expressjs/express/releases/tag/4.17.3",
"https://github.com/ljharb/qs/pull/428"
],
"uuid": "3d83a0e0-db17-448c-a5f2-f3751fd07eb0"
},
{
"affected_range": "\u003c6.2.4||\u003e=6.3.0 \u003c6.3.3||==6.4.0 ||\u003e=6.5.0 \u003c6.5.3||==6.6.0 ||\u003e=6.7.0 \u003c6.7.3||\u003e=6.8.0 \u003c6.8.3||\u003e=6.9.0 \u003c6.9.7||\u003e=6.10.0 \u003c6.10.3",
"affected_versions": "All versions before 6.2.4, all versions starting from 6.3.0 before 6.3.3, all versions starting from 6.4.0 up to 6.5.3, all versions starting from 6.6.0 up to 6.7.3, all versions starting from 6.8.0 before 6.8.3, all versions starting from 6.9.0 before 6.9.7, all versions starting from 6.10.0 before 6.10.3",
"cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"cwe_ids": [
"CWE-1035",
"CWE-1321",
"CWE-937"
],
"date": "2023-02-16",
"description": "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\u0026a[__proto__]\u0026a[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).",
"fixed_versions": [
"6.2.4",
"6.3.3",
"6.4.1",
"6.5.3",
"6.6.1",
"6.7.3",
"6.8.3",
"6.9.7",
"6.10.3"
],
"identifier": "CVE-2022-24999",
"identifiers": [
"CVE-2022-24999"
],
"not_impacted": "All versions starting from 6.2.4 before 6.3.0, all versions starting from 6.3.3 before 6.4.0, all versions after 6.5.3 before 6.6.0, all versions after 6.7.3 before 6.8.0, all versions starting from 6.8.3 before 6.9.0, all versions starting from 6.9.7 before 6.10.0, all versions starting from 6.10.3",
"package_slug": "npm/qs",
"pubdate": "2022-11-26",
"solution": "Upgrade to versions 6.2.4, 6.3.3, 6.8.3, 6.9.7, 6.10.3 or above.",
"title": "Improperly Controlled Modification of Object Prototype Attributes (\u0027Prototype Pollution\u0027)",
"urls": [
"https://nvd.nist.gov/vuln/detail/CVE-2022-24999",
"https://github.com/n8tz/CVE-2022-24999",
"https://github.com/expressjs/express/releases/tag/4.17.3",
"https://github.com/ljharb/qs/pull/428"
],
"uuid": "6311889c-6658-48b2-8c85-58502f70827c"
}
]
},
"nvd.nist.gov": {
"configurations": {
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*",
"cpe_name": [],
"versionEndExcluding": "6.3.3",
"versionStartIncluding": "6.3.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:qs_project:qs:6.4.0:*:*:*:*:node.js:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*",
"cpe_name": [],
"versionEndExcluding": "6.5.3",
"versionStartIncluding": "6.5.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:qs_project:qs:6.6.0:*:*:*:*:node.js:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*",
"cpe_name": [],
"versionEndExcluding": "6.7.3",
"versionStartIncluding": "6.7.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*",
"cpe_name": [],
"versionEndExcluding": "6.8.3",
"versionStartIncluding": "6.8.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*",
"cpe_name": [],
"versionEndExcluding": "6.9.7",
"versionStartIncluding": "6.9.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*",
"cpe_name": [],
"versionEndExcluding": "6.10.3",
"versionStartIncluding": "6.10.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*",
"cpe_name": [],
"versionEndExcluding": "6.2.4",
"vulnerable": true
}
],
"operator": "OR"
},
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:openjsf:express:*:*:*:*:*:node.js:*:*",
"cpe_name": [],
"versionEndExcluding": "4.17.3",
"vulnerable": true
}
],
"operator": "OR"
},
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
}
],
"operator": "OR"
}
]
},
"cve": {
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2022-24999"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"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\u0026a[__proto__]\u0026a[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)."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "en",
"value": "CWE-1321"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/n8tz/CVE-2022-24999",
"refsource": "MISC",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/n8tz/CVE-2022-24999"
},
{
"name": "https://github.com/expressjs/express/releases/tag/4.17.3",
"refsource": "CONFIRM",
"tags": [
"Release Notes"
],
"url": "https://github.com/expressjs/express/releases/tag/4.17.3"
},
{
"name": "https://github.com/ljharb/qs/pull/428",
"refsource": "CONFIRM",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://github.com/ljharb/qs/pull/428"
},
{
"name": "[debian-lts-announce] 20230130 [SECURITY] [DLA 3299-1] node-qs security update",
"refsource": "MLIST",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html"
},
{
"name": "https://security.netapp.com/advisory/ntap-20230908-0005/",
"refsource": "CONFIRM",
"tags": [],
"url": "https://security.netapp.com/advisory/ntap-20230908-0005/"
}
]
}
},
"impact": {
"baseMetricV3": {
"cvssV3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6
}
},
"lastModifiedDate": "2023-09-08T17:15Z",
"publishedDate": "2022-11-26T22:15Z"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…