# CVE-2019-14271: GO-2024-2521 - Moby Docker cp broken with debian containers in github.com/docker/docker

Source: https://junglewise.ai/threats/cve-2019-14271-moby-docker-cp-broken-with-debian-containers  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-06-28  
License: CC BY 4.0 with a link back

CVE-2019-14271 · Severity: low · CVSS 3.1 · Published 2024-06-28

Moby Docker cp broken with debian containers in github.com/docker/docker

Technologies: [github.com/docker/docker (Go)](https://junglewise.ai/threats/technologies/github-com-docker-docker), [github.com/moby/moby (Go)](https://junglewise.ai/threats/technologies/github-com-moby-moby). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2019-14271 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2019-14271 being exploited in the wild.

**How severe is CVE-2019-14271?** Low severity, with a CVSS score of 3.1, published 28 June 2024.

**Which products and versions are affected?** github.com/docker/docker (Go) ECOSYSTEM:introduced=19.03.0,fixed=19.03.1, SEMVER:introduced=0,fixed=20.10.0-beta1+incompatible; github.com/moby/moby (Go) SEMVER:introduced=0,fixed=20.10.0-beta1+incompatible.

**Is there a fix for CVE-2019-14271?** Yes. github.com/docker/docker (Go): upgrade to 19.03.1, 20.10.0-beta1+incompatible or later; github.com/moby/moby (Go): upgrade to 20.10.0-beta1+incompatible or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2019-14271?** Check whether you run github.com/docker/docker (Go) or github.com/moby/moby (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/docker/docker (Go): upgrade to 19.03.1, 20.10.0-beta1+incompatible or later

  ```sh
  go get github.com/docker/docker@v20.10.0-beta1+incompatible
  ```

- github.com/moby/moby (Go): upgrade to 20.10.0-beta1+incompatible or later

  ```sh
  go get github.com/moby/moby@v20.10.0-beta1+incompatible
  ```


## Affected products

- github.com/docker/docker (Go) ECOSYSTEM:introduced=19.03.0,fixed=19.03.1, SEMVER:introduced=0,fixed=20.10.0-beta1+incompatible
- github.com/moby/moby (Go) SEMVER:introduced=0,fixed=20.10.0-beta1+incompatible

## Identifiers

- CVE-2019-14271
- GHSA-v2cv-wwxq-qq97
- GO-2024-2521

## Related threats

- [Moby Docker Engine race condition in docker cp mount setup](https://junglewise.ai/threats/cve-2026-42306-moby-docker-engine-race-condition-in-docker-cp-mount-setup)
- [Moby Docker Engine symlink race condition in docker cp](https://junglewise.ai/threats/cve-2026-41568-moby-docker-engine-symlink-race-condition-in-docker-cp)
- [Moby and Docker Engine code execution via trojanized decompression binaries](https://junglewise.ai/threats/cve-2026-41567-moby-and-docker-engine-code-execution-via-trojanized)
- [Moby AuthZ plugin authorization bypass via oversized request body](https://junglewise.ai/threats/cve-2026-34040-moby-authz-plugin-authorization-bypass-via-oversized-request-body)
- [Moby privilege validation bypass in docker plugin install](https://junglewise.ai/threats/cve-2026-33997-moby-privilege-validation-bypass-in-docker-plugin-install)