dbcve.org
OnosApplication · Opennetworking

CVE-2025-29310

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue in onos v2.7.0 allows attackers to trigger a packet deserialization problem when supplying a crafted LLDP packet. This vulnerability allows attackers to execute arbitrary commands or access network information.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

ONOS v2.7.0 contains a packet deserialization vulnerability in its LLDP (Link Layer Discovery Protocol) packet parsing logic. Attackers can supply a specially crafted LLDP packet to trigger improper deserialization, potentially achieving arbitrary command execution on the affected ONOS controller or accessing sensitive network topology information.

MitigationUpgrade to a patched version of ONOS if available; otherwise, restrict network access to ONOS controllers and consider filtering or blocking LLDP traffic at network boundaries to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OnosApplication
Affected:= 2.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify ONOS is installed
    Check for ONOS processes running (e.g., ps aux | grep onos, systemctl status onos, or check for ONOS Java processes) and look for ONOS installation directories (typically /opt/onos or /usr/local/onos)
    Affected if ONOS is not installed or not running - no action needed
  2. Confirm ONOS version is 2.7.0
    Run 'onos-version' if available, or check the version file in the ONOS installation directory (such as version.properties, pom.xml, or the karaf version file under $ONOS_HOME/lib), or query the ONOS CLI with 'version' command
    Affected if Version is exactly 2.7.0 - this is the affected version; versions before or after may not be vulnerable
  3. Determine if LLDP processing is enabled
    Check ONOS packet processor configuration or intent configuration for LLDP packet handling. In ONOS CLI, use 'packet-requests' or check for active PacketProvider services. Also check if the 'lldpprovider' or 'packet' feature is loaded (list command in karaf)
    Affected if LLDP packet processing feature is actively enabled - this is the required attack surface for exploitation
  4. Review ONOS logs for LLDP anomalies
    Examine ONOS logs (typically in $ONOS_HOME/logs/onos.log or karaf.log) for entries containing 'LLDP', 'deserialization', 'packet', or suspicious stack traces around packet processing timestamps. Also check for unexpected packet-in events
    Affected if Logs show unexpected LLDP packet processing errors, deserialization exceptions, or unusual packet-in patterns from LLDP source MACs
  5. Check for external network exposure of ONOS
    Verify firewall rules and network configuration to determine if the ONOS controller management or data plane ports (typically 6653 for OpenFlow, 8181 for REST API) are accessible from untrusted networks
    Affected if ONOS controller ports are exposed to untrusted networks - combined with version 2.7.0 and enabled LLDP, this increases exploitation likelihood

You are affected if your ONOS installation is exactly version 2.7.0, LLDP packet processing is enabled, and the controller is network-accessible to potential attackers sending crafted LLDP packets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of ONOS if available; otherwise, restrict network access to ONOS controllers and consider filtering or blocking LLDP traffic at network boundaries to reduce attack surface.

Fix this in Onos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29310 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29310 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data