# CVE-2022-32389: Hardcoded credentials in n/a

> Hard-coded credentials in the Registry Editor allow attackers to access sensitive user credentials and certificates.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wfxr-7w34-vgf9

## What is CVE-2022-32389?

CVE-2022-32389 is a high-severity vulnerability in n/a, published on 14 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Isode SWIFT v4.0.2 was discovered to contain hard-coded credentials in the Registry Editor. This allows attackers to access sensitive information such as user credentials and certificates.

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

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

It affects 1 product.


Products: Isode Swift.

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

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

## Is CVE-2022-32389 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32389 is a high-severity vulnerability in n/a, published on 14 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-32389 in the wild and no public exploit code.

Affected product: n/a. 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-32389/ (Markdown: https://insights.sbomify.com/CVE-2022-32389/index.md)
```

## Sources

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

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