{"answers":{"affected":"2 open source packages ship an affected version, including github.com/docker/docker. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13509 in the wild and no public exploit code.","fix":"Upgrade github.com/docker/docker to 18.09.8 or later.","what":"CVE-2019-13509 is a high-severity vulnerability in n/a, published on 18 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-13509 and fix it if it is affected.\n\nWhat it is: CVE-2019-13509 is a high-severity vulnerability in n/a, published on 18 Jul 2019. 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-2019-13509 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/docker/docker (Go): affected all versions; fixed in 18.09.8\n- github.com/docker/docker (Go): affected all versions; fixed in 18.09.8\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-2019-13509/ (Markdown: https://insights.sbomify.com/CVE-2019-13509/index.md)","id":"CVE-2019-13509","markdown":"https://insights.sbomify.com/CVE-2019-13509/index.md","name":"CVE-2019-13509","record":{"aliases":["CLEANSTART-2026-MP51710","DEBIAN-CVE-2019-13509","GHSA-j249-ghv5-7mxv"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Docker Engine","requires_auth":"none","summary":"Docker Engine in debug mode may leak secrets into logs during stack redeployment, exposing sensitive data to attackers with log access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"docker","vendor":"docker"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"In Docker CE and EE before 18.09.8 (as well as Docker EE before 17.06.2-ee-23 and 18.x before 18.03.1-ee-10), Docker Engine in debug mode may sometimes add secrets to the debug log. This applies to a scenario where docker stack deploy is run to redeploy a stack that includes (non external) secrets. It potentially applies to other API users of the stack API if they resend the secret.","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":"Secret insertion into debug log in Docker","id":"CVE-2019-13509","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":8,"next":{"headline":"Use after free in Rockwell Automation Arena Simulation Software versions 16.00.00 and earlier","id":"CVE-2019-13510"},"packages":[{"ecosystem":"Go","fixed":["18.09.8"],"introduced":["0"],"last_affected":[],"package":"github.com/docker/docker","purl":null,"source":"GHSA-j249-ghv5-7mxv"},{"ecosystem":"Go","fixed":["18.09.8"],"introduced":["0"],"last_affected":[],"package":"github.com/docker/docker","purl":"pkg:golang/github.com/docker/docker","source":"GHSA-j249-ghv5-7mxv"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-13508"},"products":["n/a"],"published":"2019-07-18","related":[{"cvss_score":10,"headline":"Arbitrary Code Execution","id":"CVE-2014-9357","kev_date_added":null,"published":"2014-12-16"},{"cvss_score":8.8,"headline":"Privilege escalation in Docker","id":"CVE-2020-14298","kev_date_added":null,"published":"2020-07-13"},{"cvss_score":8.8,"headline":"Privilege escalation in Docker","id":"CVE-2020-14300","kev_date_added":null,"published":"2020-07-13"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2018-15514","kev_date_added":null,"published":"2018-09-01"},{"cvss_score":8.6,"headline":"Path Traversal in Docker","id":"CVE-2014-9356","kev_date_added":null,"published":"2019-12-02"},{"cvss_score":8.4,"headline":"Command injection in n/a","id":"CVE-2019-13139","kev_date_added":null,"published":"2019-08-22"},{"cvss_score":8.1,"headline":"Other in n/a","id":"CVE-2014-5282","kev_date_added":null,"published":"2018-02-06"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Docker Engine in debug mode may leak secrets into logs during stack redeployment, exposing sensitive data to attackers with log access.","url":"https://insights.sbomify.com/CVE-2019-13509/"}