# CVE-2023-31114: Information disclosure in n/a

> A crafted application can query SIM status due to incorrect resource transfer in Samsung Exynos Modem firmware, leading to information disclosure.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 7 Jun 2023
- **Updated:** 7 Jan 2025
- **Also known as:** GHSA-xfp8-8c2h-hg4q

## What is CVE-2023-31114?

CVE-2023-31114 is a critical vulnerability in n/a, published on 7 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the Shannon RCS component in Samsung Exynos Modem 5123 and 5300. Incorrect resource transfer between spheres can cause unintended querying of the SIM status via a crafted application.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

## Which versions are affected by CVE-2023-31114?

It affects 2 products.


Products: Samsung Exynos 5123 Firmware, Samsung Exynos 5300 Firmware.

## How do I fix CVE-2023-31114?

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

## Is CVE-2023-31114 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-31116](https://insights.sbomify.com/CVE-2023-31116/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-31115](https://insights.sbomify.com/CVE-2023-31115/): Privilege escalation in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31114 and fix it if it is affected.

What it is: CVE-2023-31114 is a critical vulnerability in n/a, published on 7 Jun 2023. 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-2023-31114 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-2023-31114/ (Markdown: https://insights.sbomify.com/CVE-2023-31114/index.md)
```

## Sources

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

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