# CVE-2022-43673: Information disclosure in n/a

> Attackers can retrieve deleted messages from local IndexedDB storage in the Wire desktop application, exposing sensitive communication data.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-636w-x3wj-wj9p

## What is CVE-2022-43673?

CVE-2022-43673 is a medium-severity vulnerability in n/a, published on 18 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Wire through 3.22.3993 on Windows advertises deletion of sent messages; nonetheless, all messages can be retrieved (for a limited period of time) from the AppData\Roaming\Wire\IndexedDB\https_app.wire.com_0.indexeddb.leveldb database.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Wire Wire.

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

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

## Is CVE-2022-43673 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43673 exists.

## Other vulnerabilities in n/a

- [CVE-2020-27853](https://insights.sbomify.com/CVE-2020-27853/): Other in n/a (critical 9.8)
- [CVE-2021-32665](https://insights.sbomify.com/CVE-2021-32665/): Verified groups not reliable (high 8.8)
- [CVE-2020-15258](https://insights.sbomify.com/CVE-2020-15258/): Insecure use of shell.openExternal in Wire (high 8.0)
- [CVE-2018-8909](https://insights.sbomify.com/CVE-2018-8909/): Path traversal in n/a (high 7.5)
- [CVE-2021-41093](https://insights.sbomify.com/CVE-2021-41093/): Account takeover when having only access to a user's short lived token (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43673 is a medium-severity vulnerability in n/a, published on 18 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43673 exists.

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

## Sources

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

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