# CVE-2024-27363: Information disclosure in n/a

> Attackers can exploit improper pointer checks in Samsung Exynos processors to disclose sensitive information.

- **Severity:** Medium 6.0 (`CVSS:3.1/AC:L/AV:L/A:H/C:H/I:N/PR:H/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2024
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-r884-9fgg-6q7w

## What is CVE-2024-27363?

CVE-2024-27363 is a medium-severity vulnerability in n/a, published on 9 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was discovered in Samsung Mobile Processor Exynos 850, Exynos 9610, Exynos 980, Exynos 1280, Exynos 1380, Exynos 1330, Exynos W920, and Exynos W930 where it does not properly check a pointer address, which can lead to a Information disclosure.

## Which versions are affected by CVE-2024-27363?


## How do I fix CVE-2024-27363?

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

## Is CVE-2024-27363 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27363 and fix it if it is affected.

What it is: CVE-2024-27363 is a medium-severity vulnerability in n/a, published on 9 Jul 2024. 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-2024-27363 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-2024-27363/ (Markdown: https://insights.sbomify.com/CVE-2024-27363/index.md)
```

## Sources

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

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