# CVE-2025-29311: Weak cryptography in n/a

> Attackers can brute-force private keys from limited LLDP secret space in ONOS, enabling data access and privilege escalation.

- **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:** 24 Mar 2025
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-6cpx-55pw-9cxq

## What is CVE-2025-29311?

CVE-2025-29311 is a high-severity vulnerability in n/a, published on 24 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Limited secret space in LLDP packets used in onos v2.7.0 allows attackers to obtain the private key via a bruteforce attack. Attackers are able to leverage this vulnerability into creating crafted LLDP packets.

Weakness: CWE-331 (Insufficient Entropy)

## Which versions are affected by CVE-2025-29311?

It affects 1 product.


Products: Opennetworking Onos.

## How do I fix CVE-2025-29311?

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

## Is CVE-2025-29311 being exploited?

There is no known exploitation of CVE-2025-29311 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-2025-29311 and fix it if it is affected.

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

## Sources

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

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