- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The `setPassword` method (http://parseplatform.org/Parse-SDK-JS/api/2.9.1/Parse.User.html#setPassword) stores the user's password in localStorage as raw text making it vulnerable to anyone with access to your localStorage. We believe this is the only time that password is stored at all. In the documentation under Users > Signing Up, it clearly states, "We never store passwords in plaintext, nor will we ever transmit passwords back to the client in plaintext."
Example Code: ```js async () => { const user = Parse.User.current() if (user) { user.setPassword('newpass') await user.save() } } ``` After running the above code, the new password will be stored in localStorage as a property named "password".
Proposed Solution: Before saving anything to localStorage, Parse should strip out any properties named "password" that are attempting to be stored with a Parse.User type object.
Configuration: Parse SDK: 2.9.1 Parse Server: 3.9.0
Patch / fix
Is GHSA-wvh7-5p38-2qfc in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse | <2.10.0 |
2.10.0 |
Classification
- Weakness
-
- CWE-256 Plaintext Storage of a Password
References
Sources
- GitHub Advisory GHSA-wvh7-5p38-2qfc
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.