# CVE-2022-28693: Information disclosure in Intel(R) Processors

> An authorized local user can exploit unprotected return branch target prediction in Intel processors to disclose sensitive information.

- **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:** Yes
- **Published:** 14 Feb 2025
- **Updated:** 14 Feb 2025
- **Also known as:** UBUNTU-CVE-2022-28693

## What is CVE-2022-28693?

CVE-2022-28693 is a medium-severity vulnerability in Intel(R) Processors, published on 14 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unprotected alternative channel of return branch target prediction in some Intel(R) Processors may allow an authorized user to potentially enable information disclosure via local access.

Weakness: CWE-420 (Unprotected Alternate Channel)

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


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

Apply the vendor's patch.

## Is CVE-2022-28693 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28693 is a medium-severity vulnerability in Intel(R) Processors, published on 14 Feb 2025. 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-28693 in the wild and no public exploit code.

Affected product: Intel(R) Processors. 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-28693/ (Markdown: https://insights.sbomify.com/CVE-2022-28693/index.md)
```

## Sources

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

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