Sensitive Data Exposure in parse-server
Versions of parse-server prior to 3.6.0 could allow an account enumeration attack via account linking. `ParseError.ACCOUNT_ALREADY_LINKED(208)` was thrown BEFORE the AuthController checks the password and throws a `ParseError.SESSION_MISSING(206)` for Insufficient auth. An attacker can guess ids and get information about linked accounts/email addresses. ### For more information If you have any questions or comments about this advisory, Open an issue in the [parse-server](https://github.com/parse-community/parse-server) [Parse Community Vulnerability Disclosure Program](https://github.com/parse-community/parse-server/blob/master/SECURITY.md)
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-1020013US | medium5.3 | — | ||
parse-server before 3.6.0 allows account enumeration. | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-8w3j-g983-8jh5ADVISORY
- https://github.com/parse-community/parse-server/commit/73b0f9a339b81f5d757725dc557955a7b670a3ecWEB
- https://github.com/parse-community/parse-server/security/advisories/GHSA-8w3j-g983-8jh5WEB
- https://nvd.nist.gov/vuln/detail/CVE-2019-1020013ADVISORY
- https://snyk.io/vuln/SNYK-JS-PARSESERVER-455637WEB
- https://www.npmjs.com/advisories/1114WEB
- https://www.owasp.org/index.php/Testing_for_User_Enumeration_and_Guessable_User_Account_(OWASP-AT-002)#Description_of_the_IssueWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan