{"answers":{"affected":"2 open source packages ship an affected version, including github.com/moby/moby. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16539 in the wild and no public exploit code.","fix":"Upgrade github.com/moby/moby to 17.12.0-ce or later.","what":"CVE-2017-16539 is a medium-severity missing authorization vulnerability in n/a, published on 4 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16539 and fix it if it is affected.\n\nWhat it is: CVE-2017-16539 is a medium-severity missing authorization vulnerability in n/a, published on 4 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-16539 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/moby/moby (Go): affected all versions; fixed in 17.12.0-ce\n- github.com/moby/moby (Go): affected all versions; fixed in 17.12.0-ce\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-16539/ (Markdown: https://insights.sbomify.com/CVE-2017-16539/index.md)","id":"CVE-2017-16539","markdown":"https://insights.sbomify.com/CVE-2017-16539/index.md","name":"CVE-2017-16539","record":{"aliases":["DEBIAN-CVE-2017-16539","GHSA-vfjc-2qcw-j95j","UBUNTU-CVE-2017-16539"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Docker Moby","requires_auth":"none","summary":"Attackers with container access can write to /proc/scsi to trigger SCSI device removal, causing data loss or denial of service on vulnerable Linux kernels.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"moby","vendor":"mobyproject"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The DefaultLinuxSpec function in oci/defaults.go in Docker Moby through 17.03.2-ce does not block /proc/scsi pathnames, which allows attackers to trigger data loss (when certain older Linux kernels are used) by leveraging Docker container access to write a \"scsi remove-single-device\" line to /proc/scsi/scsi, aka SCSI MICDROP.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Docker Moby /proc/scsi Path Exposure Allows Host Data Loss (SCSI MICDROP)","id":"CVE-2017-16539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":2,"n_references":5,"next":{"headline":"Information disclosure in n/a","id":"CVE-2017-16540"},"packages":[{"ecosystem":"Go","fixed":["17.12.0-ce"],"introduced":["0"],"last_affected":[],"package":"github.com/moby/moby","purl":null,"source":"GHSA-vfjc-2qcw-j95j"},{"ecosystem":"Go","fixed":["17.12.0-ce"],"introduced":["0"],"last_affected":[],"package":"github.com/moby/moby","purl":"pkg:golang/github.com/moby/moby","source":"GHSA-vfjc-2qcw-j95j"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-16538"},"products":["n/a"],"published":"2017-11-04","related":[{"cvss_score":8.1,"headline":"Moby Race Condition vulnerability","id":"CVE-2024-36623","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":7.5,"headline":"moby/moby's dockerd daemon encrypted overlay network may be unauthenticated","id":"CVE-2023-28840","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":7.5,"headline":"Docker Authentication Bypass","id":"CVE-2018-12608","kev_date_added":null,"published":"2018-09-10"},{"cvss_score":6.9,"headline":"Moby classic builder cache poisoning","id":"CVE-2024-24557","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":6.8,"headline":"moby/moby's dockerd daemon encrypted overlay network traffic may be unencrypted","id":"CVE-2023-28841","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":6.8,"headline":"moby/moby's dockerd daemon encrypted overlay network with a single endpoint is unauthenticated","id":"CVE-2023-28842","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":6.5,"headline":"NULL Pointer Dereference on moby image history","id":"CVE-2024-36620","kev_date_added":null,"published":"2024-11-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-27","vendors":["n/a"]},"summary":"Attackers with container access can write to /proc/scsi to trigger SCSI device removal, causing data loss or denial of service on vulnerable Linux kernels.","url":"https://insights.sbomify.com/CVE-2017-16539/"}