# CVE-2022-4611: Click Studios Passwordstate hard-coded credentials

> Attackers can exploit hard-coded credentials in Click Studios Passwordstate to bypass security controls and potentially take over accounts.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gc6m-vvjp-f3xm

## What is CVE-2022-4611?

CVE-2022-4611 is a medium-severity vulnerability in Click Studios Passwordstate, published on 19 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in Click Studios Passwordstate and Passwordstate Browser Extension Chrome. This affects an unknown part. The manipulation leads to hard-coded credentials. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component. The identifier VDB-216273 was assigned to this vulnerability.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-4611?

It affects 1 product.


Products: Clickstudios Passwordstate.

## How do I fix CVE-2022-4611?

No fix has been published for CVE-2022-4611 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-4611 being exploited?

There is no known exploitation of CVE-2022-4611 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Phamchie/CVE-2022-4611 (github_poc): https://github.com/Phamchie/CVE-2022-4611
- https://github.com/fgsoftware1/CVE-2022-4611 (github_poc): https://github.com/fgsoftware1/CVE-2022-4611

## Other vulnerabilities in Click Studios Passwordstate

- [CVE-2020-26061](https://insights.sbomify.com/CVE-2020-26061/): Auth bypass in n/a (high 7.5)
- [CVE-2022-3875](https://insights.sbomify.com/CVE-2022-3875/): Click Studios Passwordstate API authentication bypass by assumed-immutable data (high 7.3)
- [CVE-2020-27747](https://insights.sbomify.com/CVE-2020-27747/): Auth bypass in n/a (medium 6.8)
- [CVE-2022-25570](https://insights.sbomify.com/CVE-2022-25570/): Missing authorization in n/a (medium 6.5)
- [CVE-2018-14776](https://insights.sbomify.com/CVE-2018-14776/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4611 and fix it if it is affected.

What it is: CVE-2022-4611 is a medium-severity vulnerability in Click Studios Passwordstate, published on 19 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4611 in the wild and no public exploit code.

Affected product: Click Studios Passwordstate. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2022-4611/ (Markdown: https://insights.sbomify.com/CVE-2022-4611/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4611
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4611
- OSV: https://osv.dev/vulnerability/CVE-2022-4611

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4611/
Summaries are generated and may contain mistakes; the official description above is the record.