# CVE-2022-29486: Memory corruption in Hyperscan library maintained by Intel(R)

> An unauthenticated attacker can exploit improper buffer restrictions in the Intel Hyperscan library to achieve privilege escalation via network access.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Nov 2022
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-632q-5p2q-r532, OESA-2023-1254

## What is CVE-2022-29486?

CVE-2022-29486 is a medium-severity memory corruption vulnerability in Hyperscan library maintained by Intel(R), published on 11 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper buffer restrictions in the Hyperscan library maintained by Intel(R) all versions downloaded before 04/29/2022 may allow an unauthenticated user to potentially enable escalation of privilege via network access.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Intel Hyperscan.

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

Upgrade to a fixed version.

## Is CVE-2022-29486 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29486 is a medium-severity memory corruption vulnerability in Hyperscan library maintained by Intel(R), published on 11 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-29486 in the wild and no public exploit code.

Affected product: Hyperscan library maintained by Intel(R). 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-29486/ (Markdown: https://insights.sbomify.com/CVE-2022-29486/index.md)
```

## Sources

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

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