ghsa-8xq9-g7ch-35hg
Vulnerability from github
Published
2024-10-04 18:50
Modified
2024-10-04 18:50
Severity ?
8.1 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
8.6 (High) - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
8.6 (High) - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
VLAI Severity ?
Summary
Parse Server's custom object ID allows to acquire role privileges
Details
Impact
If the Parse Server option allowCustomObjectId: true
is set, an attacker that is allowed to create a new user can set a custom object ID for that new user that exploits the vulnerability and acquires privileges of a specific role.
Patches
Improved validation for custom user object IDs. Session tokens for existing users with an object ID that exploits the vulnerability are now rejected.
Workarounds
- Disable custom object IDs by setting
allowCustomObjectId: false
or not setting the option which defaults tofalse
. - Use a Cloud Code Trigger to validate that a new user's object ID doesn't start with the prefix
role:
.
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-8xq9-g7ch-35hg
- https://github.com/parse-community/parse-server/pull/9317 (fix for Parse Server 7)
- https://github.com/parse-community/parse-server/pull/9318 (fix for Parse Server 6)
{ "affected": [ { "package": { "ecosystem": "npm", "name": "parse-server" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "6.5.9" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "npm", "name": "parse-server" }, "ranges": [ { "events": [ { "introduced": "7.0.0" }, { "fixed": "7.3.0" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-47183" ], "database_specific": { "cwe_ids": [ "CWE-285", "CWE-863" ], "github_reviewed": true, "github_reviewed_at": "2024-10-04T18:50:56Z", "nvd_published_at": "2024-10-04T15:15:13Z", "severity": "HIGH" }, "details": "### Impact\n\nIf the Parse Server option `allowCustomObjectId: true` is set, an attacker that is allowed to create a new user can set a custom object ID for that new user that exploits the vulnerability and acquires privileges of a specific role.\n\n### Patches\n\nImproved validation for custom user object IDs. Session tokens for existing users with an object ID that exploits the vulnerability are now rejected.\n\n### Workarounds\n\n- Disable custom object IDs by setting `allowCustomObjectId: false` or not setting the option which defaults to `false`.\n- Use a Cloud Code Trigger to validate that a new user\u0027s object ID doesn\u0027t start with the prefix `role:`.\n\n### References\n\n- https://github.com/parse-community/parse-server/security/advisories/GHSA-8xq9-g7ch-35hg\n- https://github.com/parse-community/parse-server/pull/9317 (fix for Parse Server 7)\n- https://github.com/parse-community/parse-server/pull/9318 (fix for Parse Server 6)", "id": "GHSA-8xq9-g7ch-35hg", "modified": "2024-10-04T18:50:56Z", "published": "2024-10-04T18:50:56Z", "references": [ { "type": "WEB", "url": "https://github.com/parse-community/parse-server/security/advisories/GHSA-8xq9-g7ch-35hg" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47183" }, { "type": "WEB", "url": "https://github.com/parse-community/parse-server/pull/9317" }, { "type": "WEB", "url": "https://github.com/parse-community/parse-server/pull/9318" }, { "type": "WEB", "url": "https://github.com/parse-community/parse-server/commit/13ee52f0d19ef3a3524b3d79aea100e587eb3cfc" }, { "type": "WEB", "url": "https://github.com/parse-community/parse-server/commit/1bfbccf9ee7ea77533b2b2aa7c4c69f3bd35e66f" }, { "type": "PACKAGE", "url": "https://github.com/parse-community/parse-server" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" }, { "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N", "type": "CVSS_V4" } ], "summary": "Parse Server\u0027s custom object ID allows to acquire role privileges" }
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…