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

> An attacker with temporary SMS access can steal IMAP credentials to read voice mail messages without user interaction.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8j23-w6cm-fq4q

## What is CVE-2022-23835?

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

### Official description

The Visual Voice Mail (VVM) application through 2022-02-24 for Android allows persistent access if an attacker temporarily controls an application that has the READ_SMS permission, and reads an IMAP credentialing message that is (by design) not displayed to the victim within the AOSP SMS/MMS messaging application. (Often, the IMAP credentials are usable to listen to voice mail messages sent before the vulnerability was exploited, in addition to new ones.) NOTE: some vendors characterize this as not a "concrete and exploitable risk.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Visual Voice Mail Project Visual Voice Mail.

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

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

## Is CVE-2022-23835 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23835 is a high-severity vulnerability in n/a, published on 25 Feb 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-23835 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-23835/ (Markdown: https://insights.sbomify.com/CVE-2022-23835/index.md)
```

## Sources

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

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