# GHSA-wvh7-5p38-2qfc: Storing Password in Local Storage

> The Parse JavaScript SDK stores user passwords in plaintext in localStorage, allowing attackers with local access to steal credentials.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2020

## What is GHSA-wvh7-5p38-2qfc?

GHSA-wvh7-5p38-2qfc is a vulnerability in parse, published on 23 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

## Which versions are affected by GHSA-wvh7-5p38-2qfc?

2 open source packages ship an affected version, including parse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `parse` | npm | All versions | 2.10.0 |
| `parse` | npm | All versions | 2.10.0 |

## How do I fix GHSA-wvh7-5p38-2qfc?

Upgrade parse to 2.10.0 or later.

## Is GHSA-wvh7-5p38-2qfc being exploited?

There is no known exploitation of GHSA-wvh7-5p38-2qfc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wvh7-5p38-2qfc and fix it if it is affected.

What it is: GHSA-wvh7-5p38-2qfc is a vulnerability in parse, published on 23 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-wvh7-5p38-2qfc in the wild and no public exploit code.

Affected packages and fixed versions:
- parse (npm): affected all versions; fixed in 2.10.0
- parse (npm): affected all versions; fixed in 2.10.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-wvh7-5p38-2qfc/ (Markdown: https://insights.sbomify.com/GHSA-wvh7-5p38-2qfc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wvh7-5p38-2qfc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wvh7-5p38-2qfc/
Summaries are generated and may contain mistakes; the official description above is the record.