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

> A local attacker can access unauthorized information via a pointer-alignment flaw in SCONE Confidential Computing Platform.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/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:** 30 Dec 2023
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-cv25-rx3c-9hpp

## What is CVE-2023-38023?

CVE-2023-38023 is a medium-severity vulnerability in n/a, published on 30 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in SCONE Confidential Computing Platform before 5.8.0 for Intel SGX. Lack of pointer-alignment logic in __scone_dispatch and other entry functions allows a local attacker to access unauthorized information, aka an "AEPIC Leak."

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

It affects 1 product.


Products: Scontain Scone.

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

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

## Is CVE-2023-38023 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-29971](https://insights.sbomify.com/CVE-2024-29971/): Race condition in n/a (critical 9.8)
- [CVE-2022-46487](https://insights.sbomify.com/CVE-2022-46487/): Information disclosure in n/a (high 7.8)
- [CVE-2022-46486](https://insights.sbomify.com/CVE-2022-46486/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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