gsd-2022-31089
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions certain types of invalid files requests are not handled properly and can crash the server. If you are running multiple Parse Server instances in a cluster, the availability impact may be low; if you are running Parse Server as single instance without redundancy, the availability impact may be high. This issue has been addressed in versions 4.10.12 and 5.2.3. Users are advised to upgrade. There are no known workarounds for this issue.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2022-31089", "description": "Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions certain types of invalid files requests are not handled properly and can crash the server. If you are running multiple Parse Server instances in a cluster, the availability impact may be low; if you are running Parse Server as single instance without redundancy, the availability impact may be high. This issue has been addressed in versions 4.10.12 and 5.2.3. Users are advised to upgrade. There are no known workarounds for this issue.", "id": "GSD-2022-31089" }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2022-31089" ], "details": "Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions certain types of invalid files requests are not handled properly and can crash the server. If you are running multiple Parse Server instances in a cluster, the availability impact may be low; if you are running Parse Server as single instance without redundancy, the availability impact may be high. This issue has been addressed in versions 4.10.12 and 5.2.3. Users are advised to upgrade. There are no known workarounds for this issue.", "id": "GSD-2022-31089", "modified": "2023-12-13T01:19:18.247630Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2022-31089", "STATE": "PUBLIC", "TITLE": "Invalid file request can crashe parse-server" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "parse-server", "version": { "version_data": [ { "version_value": "\u003c 4.10.12" }, { "version_value": "\u003e=5.0.0, \u003c 5.2.3" } ] } } ] }, "vendor_name": "parse-community" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions certain types of invalid files requests are not handled properly and can crash the server. If you are running multiple Parse Server instances in a cluster, the availability impact may be low; if you are running Parse Server as single instance without redundancy, the availability impact may be high. This issue has been addressed in versions 4.10.12 and 5.2.3. Users are advised to upgrade. There are no known workarounds for this issue." } ] }, "impact": { "cvss": { "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" } }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "CWE-706: Use of Incorrectly-Resolved Name or Reference" } ] }, { "description": [ { "lang": "eng", "value": "CWE-252: Unchecked Return Value" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/parse-community/parse-server/security/advisories/GHSA-xw6g-jjvf-wwf9", "refsource": "CONFIRM", "url": "https://github.com/parse-community/parse-server/security/advisories/GHSA-xw6g-jjvf-wwf9" }, { "name": "https://github.com/parse-community/parse-server/commit/5be375dec2fa35425c1003ae81c55995ac72af92", "refsource": "MISC", "url": "https://github.com/parse-community/parse-server/commit/5be375dec2fa35425c1003ae81c55995ac72af92" } ] }, "source": { "advisory": "GHSA-xw6g-jjvf-wwf9", "discovery": "UNKNOWN" } }, "gitlab.com": { "advisories": [ { "affected_range": "\u003c4.10.12||\u003e=5.0.0 \u003c5.2.3", "affected_versions": "All versions before 4.10.12, all versions starting from 5.0.0 before 5.2.3", "cvss_v2": "AV:N/AC:L/Au:N/C:N/I:N/A:P", "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-252", "CWE-937" ], "date": "2022-07-07", "description": "Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions certain types of invalid files requests are not handled properly and can crash the server. If you are running multiple Parse Server instances in a cluster, the availability impact may be low; if you are running Parse Server as single instance without redundancy, the availability impact may be high. This issue has been addressed in versions 4.10.12 and 5.2.3. Users are advised to upgrade. There are no known workarounds for this issue.", "fixed_versions": [ "4.10.12", "5.2.3" ], "identifier": "CVE-2022-31089", "identifiers": [ "CVE-2022-31089", "GHSA-xw6g-jjvf-wwf9", "GMS-2022-2518" ], "not_impacted": "All versions starting from 4.10.12 before 5.0.0, all versions starting from 5.2.3", "package_slug": "npm/parse-server", "pubdate": "2022-06-27", "solution": "Upgrade to versions 4.10.12, 5.2.3 or above.", "title": "Unchecked Return Value", "urls": [ "https://nvd.nist.gov/vuln/detail/CVE-2022-31089", "https://github.com/parse-community/parse-server/security/advisories/GHSA-xw6g-jjvf-wwf9", "https://github.com/parse-community/parse-server/commit/5be375dec2fa35425c1003ae81c55995ac72af92", "https://github.com/advisories/GHSA-xw6g-jjvf-wwf9" ], "uuid": "825ed3a5-536b-46de-ad57-57796dae0c26" }, { "affected_range": "\u003c0", "affected_versions": "All versions before 4.10.12, all versions starting from 5.0.0 before 5.2.3", "cwe_ids": [ "CWE-1035", "CWE-937" ], "date": "2022-06-20", "description": "### Impact\nCertain types of invalid files requests are not handled properly and can crash the server. If you are running multiple Parse Server instances in a cluster, the availability impact may be low; if you are running Parse Server as a single instance without redundancy, the availability impact may be high.\n\n### Patches\nTo prevent this, invalid requests are now properly handled.\n\n### Workarounds\nNone\n\n### References\n- https://github.com/parse-community/parse-server/security/advisories/GHSA-xw6g-jjvf-wwf9\n- https://github.com/parse-community/parse-server\n\n### For more information\n- For questions or comments about this vulnerability visit our [community forum](http://community.parseplatform.org/) or [community chat](http://chat.parseplatform.org/)\n- Report other vulnerabilities at [report.parseplatform.org](https://report.parseplatform.org/)\n", "fixed_versions": [ "4.10.12", "5.2.3" ], "identifier": "GMS-2022-2518", "identifiers": [ "GHSA-xw6g-jjvf-wwf9", "GMS-2022-2518", "CVE-2022-31089" ], "not_impacted": "All versions starting from 4.10.12 before 5.0.0, all versions starting from 5.2.3", "package_slug": "npm/parse-server", "pubdate": "2022-06-20", "solution": "Upgrade to versions 4.10.12, 5.2.3 or above.", "title": "Duplicate of ./npm/parse-server/CVE-2022-31089.yml", "urls": [ "https://github.com/parse-community/parse-server/security/advisories/GHSA-xw6g-jjvf-wwf9", "https://github.com/advisories/GHSA-xw6g-jjvf-wwf9" ], "uuid": "50c3818a-a1cf-4e5f-a9dc-824cc161f73a" } ] }, "nvd.nist.gov": { "configurations": { "CVE_data_version": "4.0", "nodes": [ { "children": [], "cpe_match": [ { "cpe23Uri": "cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:node.js:*:*", "cpe_name": [], "versionEndExcluding": "5.2.3", "versionStartIncluding": "5.0.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:node.js:*:*", "cpe_name": [], "versionEndExcluding": "4.10.12", "vulnerable": true } ], "operator": "OR" } ] }, "cve": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2022-31089" }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "en", "value": "Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions certain types of invalid files requests are not handled properly and can crash the server. If you are running multiple Parse Server instances in a cluster, the availability impact may be low; if you are running Parse Server as single instance without redundancy, the availability impact may be high. This issue has been addressed in versions 4.10.12 and 5.2.3. Users are advised to upgrade. There are no known workarounds for this issue." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "en", "value": "CWE-252" }, { "lang": "en", "value": "CWE-706" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/parse-community/parse-server/security/advisories/GHSA-xw6g-jjvf-wwf9", "refsource": "CONFIRM", "tags": [ "Third Party Advisory" ], "url": "https://github.com/parse-community/parse-server/security/advisories/GHSA-xw6g-jjvf-wwf9" }, { "name": "https://github.com/parse-community/parse-server/commit/5be375dec2fa35425c1003ae81c55995ac72af92", "refsource": "MISC", "tags": [ "Patch", "Third Party Advisory" ], "url": "https://github.com/parse-community/parse-server/commit/5be375dec2fa35425c1003ae81c55995ac72af92" } ] } }, "impact": { "baseMetricV2": { "acInsufInfo": false, "cvssV2": { "accessComplexity": "LOW", "accessVector": "NETWORK", "authentication": "NONE", "availabilityImpact": "PARTIAL", "baseScore": 5.0, "confidentialityImpact": "NONE", "integrityImpact": "NONE", "vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:P", "version": "2.0" }, "exploitabilityScore": 10.0, "impactScore": 2.9, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "severity": "MEDIUM", "userInteractionRequired": false }, "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": "2022-07-07T18:37Z", "publishedDate": "2022-06-27T21:15Z" } } }
Loading…
Loading…
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.
Loading…
Loading…