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

> Attackers exploit shared branch history to infer protected information via speculative execution side channels.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/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:** 9 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5257-57v8-vjc5

## What is CVE-2022-25368?

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

### Official description

Spectre BHB is a variant of Spectre-v2 in which malicious code uses the shared branch history (stored in the CPU BHB) to influence mispredicted branches in the victim's hardware context. Speculation caused by these mispredicted branches can then potentially be used to cause cache allocation, which can then be used to infer information that should be protected.

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

It affects 22 products.


Products: Amperecomputing Ampere Altra Firmware, Amperecomputing Ampere Altra Max Firmware, Arm Cortex-A15 Firmware, Arm Cortex-A57 Firmware, Arm Cortex-A65 Firmware, Arm Cortex-A65ae Firmware, Arm Cortex-A710 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, Arm Cortex-A78ae Firmware, Arm Cortex-A78c Firmware, Arm Cortex-X1 Firmware, Arm Cortex-X2 Firmware, Arm Neoverse-E1 Firmware, Arm Neoverse-V1 Firmware and 2 more.

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

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

## Is CVE-2022-25368 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-46892](https://insights.sbomify.com/CVE-2022-46892/): Security feature bypass in n/a (critical 9.8)
- [CVE-2022-32295](https://insights.sbomify.com/CVE-2022-32295/): Security feature bypass in n/a (critical 9.8)
- [CVE-2022-37459](https://insights.sbomify.com/CVE-2022-37459/): Other in n/a (high 7.8)
- [CVE-2021-45454](https://insights.sbomify.com/CVE-2021-45454/): Information disclosure in n/a (high 7.5)
- [CVE-2022-35888](https://insights.sbomify.com/CVE-2022-35888/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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