Read the docs
TI-2020-19416 Aliases GHSA-wvh7-5p38-2qfc

Storing Password in Local Storage

Priority LOW 38CWE-256Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Information disclosure
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-256.

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

Why it matters now

Fix Fixed parse (npm): 2.10.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—parse (npm)before 2.10.02.10.0Patch availableGHSA-wvh7-5p38-2qfc
  • parse (npm) Vendor— Affected before 2.10.0 Fixed in 2.10.0 Patch available GHSA-wvh7-5p38-2qfc

Remediation

  • Fix · GHSA-wvh7-5p38-2qfc parse (npm) Fixed in 2.10.0 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-wvh7-5p38-2qfc

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences