{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-1802 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-1802 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-1802 is a medium-severity vulnerability in Docker Desktop, published on 6 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-1802 and fix it if it is affected.\n\nWhat it is: CVE-2023-1802 is a medium-severity vulnerability in Docker Desktop, published on 6 Apr 2023. 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-2023-1802 in the wild and no public exploit code.\n\nAffected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2023-1802/ (Markdown: https://insights.sbomify.com/CVE-2023-1802/index.md)","id":"CVE-2023-1802","markdown":"https://insights.sbomify.com/CVE-2023-1802/index.md","name":"CVE-2023-1802","record":{"aliases":["GHSA-44rc-4548-4794"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Docker Desktop","requires_auth":"none","summary":"Docker Desktop may leak registry credentials over HTTP if HTTPS health checks fail, requiring network sniffing to exploit.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[{"product":"desktop","vendor":"docker"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"In Docker Desktop 4.17.x the Artifactory Integration falls back to sending registry credentials over plain HTTP if the HTTPS health check has failed. A targeted network sniffing attack can lead to a disclosure of sensitive information. Only users who have Access Experimental Features enabled and have logged in to a private registry are affected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in Docker Desktop","id":"CVE-2023-1802","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Authentication Bypass in Redline Router","id":"CVE-2023-1803"},"packages":[],"prev":{"headline":"Memory corruption in tcpdump","id":"CVE-2023-1801"},"products":["Docker Desktop"],"published":"2023-04-06","related":[{"cvss_score":9,"headline":"Code injection in Docker Desktop","id":"CVE-2024-8695","kev_date_added":null,"published":"2024-09-12"},{"cvss_score":8.9,"headline":"Code injection in Docker Desktop","id":"CVE-2024-8696","kev_date_added":null,"published":"2024-09-12"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2022-37326","kev_date_added":null,"published":"2023-04-27"},{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2021-37841","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":7.3,"headline":"Elevation of Privilege in Docker Desktop for Windows during Upgrade due to Insecure Directory Deletion","id":"CVE-2025-3224","kev_date_added":null,"published":"2025-04-28"},{"cvss_score":7.3,"headline":"Privilege escalation in Docker Desktop","id":"CVE-2024-6222","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":7.1,"headline":"Docker Desktop before 4.6.0 on Windows allows attackers to delete any file through the hyperv/destroy dockerBackendV2 API via a symlink in t","id":"CVE-2022-31647","kev_date_added":null,"published":"2023-04-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-02-10","vendors":["Docker"]},"summary":"Docker Desktop may leak registry credentials over HTTP if HTTPS health checks fail, requiring network sniffing to exploit.","url":"https://insights.sbomify.com/CVE-2023-1802/"}