dbcve.org
ContikiOperating system · Contiki Os

CVE-2017-7296

MEDIUM · 6.1 CVSS v3.0 Published 2017-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 was discovered in Contiki Operating System 3.0. A Persistent XSS vulnerability is present in the MQTT/IBM Cloud Config page (aka mqtt.html) of cc26xx-web-demo. The cc26xx-web-demo features a webserver that runs on a constrained device. That particular page allows a user to remotely configure that device's operation by sending HTTP POST requests. The vulnerability consists of improper input sanitisation of the text fields on the MQTT/IBM Cloud config page, allowing for JavaScript code injection.

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

A persistent XSS vulnerability exists in the Contiki OS 3.0 cc26xx-web-demo application's MQTT/IBM Cloud configuration page (mqtt.html). The webserver running on the constrained CC26xx device fails to properly sanitize user input in text fields during HTTP POST requests, allowing injected JavaScript code to be stored and executed when the page is subsequently loaded by other users.

MitigationImplement robust input validation and output encoding on all text fields in the mqtt.html configuration page. All user-supplied data must be sanitized server-side before storage and HTML-context encoded before display to prevent script injection.

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
ContikiOperating system
Affected:= 3.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/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 checks

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

  1. Identify Contiki OS version
    Check the Contiki OS version running on the CC26xx device by examining the system information or firmware metadata. Look for 'Contiki 3.0' or 'contiki-3.0' in the firmware build information.
    Affected if The device runs Contiki OS version 3.0 exactly.
  2. Verify cc26xx-web-demo application is deployed
    Check if the cc26xx-web-demo application is included in the firmware or running on the device. This demo application includes the MQTT/IBM Cloud configuration functionality.
    Affected if The cc26xx-web-demo application is present and running on the device.
  3. Confirm webserver is active on the device
    Verify that the embedded webserver is running on the CC26xx device by attempting to access it via HTTP on the device's IP address.
    Affected if The webserver is enabled and accessible via HTTP.
  4. Locate the mqtt.html configuration page
    Access the MQTT configuration page by navigating to /mqtt.html or similar path on the device's webserver. The page is used for IBM Cloud MQTT broker configuration.
    Affected if The mqtt.html configuration page is accessible.
  5. Test for input sanitization on POST parameters
    Send an HTTP POST request to the mqtt.html page with a test script payload in a text field (such as <script>alert(1)</script>) and observe if the value is reflected without encoding when the page is reloaded.
    Affected if User-supplied text field input is stored and displayed without proper HTML encoding, allowing script execution.

A user is affected if their CC26xx device runs Contiki OS 3.0 with the cc26xx-web-demo application, the webserver is enabled, and the mqtt.html page reflects unsanitized user input from POST requests in the displayed HTML.

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 robust input validation and output encoding on all text fields in the mqtt.html configuration page. All user-supplied data must be sanitized server-side before storage and HTML-context encoded before display to prevent script injection.

Fix this in Contiki Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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