# CVE-2022-24003: Information disclosure in Bixby Vision

> Attackers can access internal data of Bixby Vision via unprotected intents, exposing sensitive information to malicious applications.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f988-rprv-54mm

## What is CVE-2022-24003?

CVE-2022-24003 is a medium-severity vulnerability in Samsung Mobile Bixby Vision, published on 11 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Exposure of Sensitive Information vulnerability in Bixby Vision prior to version 3.7.50.6 allows attackers to access internal data of Bixby Vision via unprotected intent.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Samsung Bixby Vision.

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

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

## Is CVE-2022-24003 being exploited?

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

## Other vulnerabilities in Samsung Mobile Bixby Vision

- [CVE-2023-21431](https://insights.sbomify.com/CVE-2023-21431/): Information disclosure in Bixby Vision (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24003 is a medium-severity vulnerability in Samsung Mobile Bixby Vision, published on 11 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24003 in the wild and no public exploit code.

Affected product: Samsung Mobile Bixby Vision. 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-24003/ (Markdown: https://insights.sbomify.com/CVE-2022-24003/index.md)
```

## Sources

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

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