# CVE-2022-29605: An issue was discovered in ONOS 2.5.1.


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Apr 2023
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-wq7p-5x5c-phqr

## What is CVE-2022-29605?

CVE-2022-29605 is a high-severity vulnerability in n/a, published on 20 Apr 2023. 

### Official description

An issue was discovered in ONOS 2.5.1. IntentManager attempts to install the IPv6 flow rules of an intent into an OpenFlow 1.0 switch that does not support IPv6. Improper handling of the difference in capabilities of the intent and switch is misleading to a network operator.

Weakness: CWE-670 (Always-Incorrect Control Flow Implementation)

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

It affects 1 product.


Products: Opennetworking Onos.

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

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

## Is CVE-2022-29605 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-41591](https://insights.sbomify.com/CVE-2023-41591/): Other in n/a (critical 9.8)
- [CVE-2025-29310](https://insights.sbomify.com/CVE-2025-29310/): Deserialization in n/a (critical 9.8)
- [CVE-2022-29604](https://insights.sbomify.com/CVE-2022-29604/): Business logic in n/a (critical 9.8)
- [CVE-2022-29606](https://insights.sbomify.com/CVE-2022-29606/): Business logic in n/a (critical 9.8)
- [CVE-2025-29312](https://insights.sbomify.com/CVE-2025-29312/): Business logic in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29605 is a high-severity vulnerability in n/a, published on 20 Apr 2023. 
Exploitation: There is no known exploitation of CVE-2022-29605 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-29605/ (Markdown: https://insights.sbomify.com/CVE-2022-29605/index.md)
```

## Sources

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

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