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

> ARMv8 AES instructions lack intrinsic resistance to side-channel attacks, potentially allowing attackers to recover sensitive cryptographic keys.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 10 Jan 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-x75h-jr86-mj5x

## What is CVE-2022-48251?

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

### Official description

The AES instructions on the ARMv8 platform do not have an algorithm that is "intrinsically resistant" to side-channel attacks. NOTE: the vendor reportedly offers the position "while power side channel attacks ... are possible, they are not directly caused by or related to the Arm architecture."

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 10 products.


Products: Arm Cortex-A53 Firmware, Arm Cortex-A55 Firmware, Arm Cortex-A57 Firmware, Arm Cortex-A72 Firmware, Arm Cortex-A73 Firmware, Arm Cortex-A75 Firmware, Arm Cortex-A76 Firmware, Arm Cortex-A76ae Firmware, Arm Cortex-A77 Firmware, Arm Cortex-A78 Firmware.

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

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

## Is CVE-2022-48251 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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