CVE-2017-1000078
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 · uneditedLinux foundation ONOS 1.9 is vulnerable to XSS in the device. registration
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 confidenceONOS 1.9 contains a stored Cross-Site Scripting (XSS) vulnerability in the device registration component. Attackers can inject malicious JavaScript code through device registration fields that gets executed when other users view the device information.
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= 1.8.0= 1.9.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed ONOS versionRun 'onos-version' command from the ONOS CLI or check the /opt/onos/version file if you have shell access. Alternatively, the version is displayed in the ONOS GUI login page footer or in the 'onos:version' command output from the CLI.Affected if The installed version is 1.8.0 or 1.9.0 exactly (these are the affected versions per the CVE)
-
Verify device management UI is accessibleLog into the ONOS web GUI (typically at port 8181) and navigate to the Devices view (Workflows > Device Inventory > Devices). Check if you can access the device registration functionality or API endpoint at /onos/v1/devicesAffected if You can access the device registration interface and add new devices without additional authentication beyond basic ONOS login
-
Check user roles with device registration permissionsIn ONOS UI, go to Users section (Operations > Users) or use 'onos:users' CLI command to list users and their roles. Determine if any non-admin users have access to register or add devices.Affected if Non-admin or untrusted users have permissions to access device registration, allowing them to inject XSS payloads
You are affected if running ONOS exactly version 1.8.0 or 1.9.0 AND the device registration feature is accessible to users who can submit device information that gets stored and displayed to others.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper input validation and output encoding on all device registration fields to sanitize user-supplied data before rendering. Upgrade to a patched version if available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1000078 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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