dbcve.org
OnosApplication · Onosproject

CVE-2017-1000080

HIGH · 7.5 CVSS v3.1 Published 2017-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Linux foundation ONOS 1.9.0 allows unauthenticated use of websockets.

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 · low confidence

ONOS 1.9.0 permits unauthenticated connections to websocket endpoints, allowing unauthorized parties to potentially interact with the SDN controller's management and control plane functionality without proper authentication.

MitigationImplement authentication and authorization enforcement for all websocket connections, requiring valid credentials or session tokens before permitting access to any ONOS websocket functionality.

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:= 1.8.0= 1.9.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
None
Integrity
High
Availability
None

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

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. Identify installed ONOS version
    Run 'onos-version' command or check the ONOS startup logs for the version number
    Affected if Version is 1.8.0 or 1.9.0
  2. Determine if REST API is exposed without authentication
    Check ONOS configuration files for web security settings, typically in /opt/onos/conf or similar config directories, or attempt unauthenticated HTTP requests to the ONOS REST API port (8181)
    Affected if REST API responds without requiring authentication credentials
  3. Verify websocket endpoint accessibility
    Attempt to connect to ONOS websocket endpoint (typically at /onos/ui/ws or /ws) using a websocket client without providing authentication tokens
    Affected if Websocket connection is established without requiring authentication credentials or session tokens
  4. Confirm websocket functional access
    Send websocket messages to interact with ONOS management or control plane APIs without any credentials
    Affected if Commands executed via websocket are processed without authentication validation

The environment is affected if ONOS version is 1.8.0 or 1.9.0 AND websocket endpoints accept connections without requiring authentication credentials.

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

Implement authentication and authorization enforcement for all websocket connections, requiring valid credentials or session tokens before permitting access to any ONOS websocket functionality.

Fix this in Onos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000080 — 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-2017-1000080 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