dbcve.org
Triton DatacenterApplication · Joyent

CVE-2017-10940

HIGH · 8.8 CVSS v3.0 Published 2017-10-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Joyent Smart Data Center prior to [email protected] (e469cf49-4de3-4658-8419-ab42837916ad). An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the docker API. The process does not properly validate user-supplied data which can allow for the upload of arbitrary files. An attacker can leverage this vulnerability to execute arbitrary code under the context of root. Was ZDI-CAN-3853.

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

This vulnerability in Joyent Smart Data Center's Docker API allows remote attackers with existing low-privileged code execution to upload arbitrary files due to improper validation of user-supplied data. The flaw enables escalation to root-level code execution. The vulnerability was addressed in [email protected].

MitigationUpgrade the Joyent Smart Data Center agents to version [email protected] or later, and restrict Docker API access to trusted users only as a defense-in-depth measure.

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
Triton DatacenterApplication
Affected:all versions

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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. Confirm Joyent Triton Datacenter deployment
    Identify if your infrastructure uses Joyent Triton (formerly Smart Data Center) by checking system documentation, cloud management APIs, or running 'triton --version' or 'sdc-version' if available on the host.
    Affected if The environment is Joyent Triton Datacenter and the agentsshar version is earlier than 1.0.0-release-20160901-20160901T051624Z-g3fd5adf.
  2. Check agentsshar version
    Locate and inspect the agentsshar package version on Triton compute nodes or zone controllers. This typically requires access to the Triton infrastructure API or checking the package manifest on the management nodes.
    Affected if The installed agentsshar version is below 1.0.0-release-20160901-20160901T051624Z-g3fd5adf.
  3. Verify Docker API exposure
    Review network access controls, firewall rules, and Docker daemon configuration to determine if the Docker API is accessible to network segments outside of trusted administration ranges.
    Affected if The Docker API is exposed to untrusted network segments or users without proper authentication controls.
  4. Assess existing code execution access
    Audit user accounts, deployed containers, and application permissions to determine whether any low-privileged code execution capabilities exist that could be leveraged as an initial attack vector.
    Affected if Untrusted users or processes have any form of code execution capability within the Triton environment.

A user is affected if they run Joyent Triton Datacenter with agentsshar version earlier than 1.0.0-release-20160901-20160901T051624Z-g3fd5adf, have Docker API accessible to untrusted actors, and maintain any exploitable low-privileged code execution paths.

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 the Joyent Smart Data Center agents to version [email protected] or later, and restrict Docker API access to trusted users only as a defense-in-depth measure.

Fix this in Triton Datacenter Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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