p PatchFirst

PatchFirst · Latest vulnerabilities

docker.io vulnerabilities · Page 3

Vulnerabilities published for docker.io in the last 30 days: 2. Listed in the KEV catalogue: 0.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 54

  1. CVE-2017-16539

    Medium · CVSS 5.9EPSS 1.83%Fix available

    CVE-2017-16539

    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.

    • Update to 1.13.1~ds3-1
    Published Updated
  2. CVE-2017-14992

    Medium · CVSS 6.5EPSS 2.45%Fix available

    CVE-2017-14992

    Lack of content verification in Docker-CE (Also known as Moby) versions 1.12.6-0, 1.10.3, 17.03.0, 17.03.1, 17.03.2, 17.06.0, 17.06.1, 17.06.2, 17.09.0, and earlier allows a remote attacker to cause a Denial of Service via a crafted image layer payload, aka gzip bombing.

    • Update to 18.03.1+dfsg1-2
    Published Updated
  3. CVE-2016-9962

    Medium · CVSS 6.4EPSS 0.41%Fix available

    CVE-2016-9962

    RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container.

    • Update to 1.13.1~ds1-2
    Published Updated
  4. CVE-2014-5277

    Not ratedEPSS 1.87%Fix available

    CVE-2014-5277

    Docker before 1.3.1 and docker-py before 0.5.3 fall back to HTTP when the HTTPS connection to the registry fails, which allows man-in-the-middle attackers to conduct downgrade attacks and obtain authentication and image data by leveraging a network position between the client and the registry to block HTTPS traffic.

    • Update to 1.3.1~dfsg1-1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →