Overview 139 matches · 8 in Waratek scope · 1 protected · 2 exploited · 1 CISA KEV · 7 public PoC · 1 EPSS ≥ 0.5
139matches
8in Waratek scope5.8%
1protected0.7%
2exploited1.4%
1CISA KEV0.7%
7public PoC5.0%
1EPSS ≥ 0.50.7%
Protected by Waratek
1
0.7%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
7
5.0%
Outside Waratek scope
3
2.2%
Not applicable
128
92.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
0.7%
partly blocked
0
0.0%
not blocked
138
99.3%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 29 / year
20041
Not applicable1
High1
not blocked1
No public exploit1
20050
20060
20070
20080
20090
20100
20110
20120
20130
20146
Not applicable6
High3
Medium3
not blocked6
No public exploit6
20154
Not applicable4
High2
Medium1
Low1
not blocked4
No public exploit4
20163
Not applicable3
High2
Medium1
not blocked3
No public exploit3
20177
No exploit published1
Not applicable6
High2
Medium5
not blocked7
No public exploit7
20185
Not applicable5
High4
Medium1
not blocked5
No public exploit5
201915
No exploit published1
Outside Waratek scope1
Not applicable13
Critical2
High10
Medium3
not blocked15
Exploited2
No public exploit13
202029
Not applicable29
Critical23
High4
Medium2
not blocked29
Working exploit published1
No public exploit28
20218
Outside Waratek scope2
Not applicable6
Critical3
High2
Medium3
not blocked8
No public exploit8
202211
Protected by Waratek1
No exploit published1
Not applicable9
Critical2
High6
Medium3
blocked by ARMR today1
not blocked10
Proof of concept only1
No public exploit10
202314
No exploit published2
Not applicable12
Critical3
High7
Medium4
not blocked14
Proof of concept only1
No public exploit13
202419
No exploit published2
Not applicable17
Critical3
High11
Medium5
not blocked19
Working exploit published2
Proof of concept only3
No public exploit14
202512
Not applicable12
Critical3
High3
Medium5
Low1
not blocked12
Working exploit published1
Proof of concept only1
No public exploit10
20265
Not applicable5
Critical2
High3
not blocked5
Working exploit published1
Proof of concept only1
No public exploit3
200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2014-9356 | High | 2019-12-02 | Not applicable | No public exploit | Path traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a container protection mechanism via a full pathname in a symlink in an (1) image or (2) build in a Dockerfile. |
| CVE-2019-16884 | High | 2019-09-25 | Not applicable | No public exploit | runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory. |
| CVE-2019-15752 | High | 2019-08-28 | Not applicable | Exploited | Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-credential-wincred.exe file in %PROGRAMDATA%\DockerDesktop\version-bin\ as a low-privilege user, and then waiting for an admin or service user to authenticate with Docker, restart Docker, or run 'docker login' to force the command. |
| CVE-2019-13139 | High | 2019-08-22 | Not applicable | No public exploit | In Docker before 18.09.4, an attacker who is capable of supplying or manipulating the build path for the "docker build" command would be able to gain command execution. An issue exists in the way "docker build" processes remote git URLs, and results in command injection into the underlying "git clone" command, leading to code execution in the context of the user executing the "docker build" command. This occurs because git ref can be misinterpreted as a flag. |
| CVE-2019-14271 | Critical | 2019-07-29 | Not applicable | No public exploit | In Docker 19.03.x before 19.03.1 linked against the GNU C Library (aka glibc), code injection can occur when the nsswitch facility dynamically loads a library inside a chroot that contains the contents of the container. |
| CVE-2019-13509 | High | 2019-07-18 | Not applicable | No public exploit | 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. |
| CVE-2019-10342 | Medium | 2019-07-11 | Not applicable | No public exploit | A missing permission check in Jenkins Docker Plugin 1.1.6 and earlier in various 'fillCredentialsIdItems' methods allowed users with Overall/Read access to enumerate credentials ID of credentials stored in Jenkins. |
| CVE-2019-10341 | Medium | 2019-07-11 | Not applicable | No public exploit | A missing permission check in Jenkins Docker Plugin 1.1.6 and earlier in DockerAPI.DescriptorImpl#doTestConnection allowed users with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. |
| CVE-2019-10340 | High | 2019-07-11 | Not applicable | No public exploit | A cross-site request forgery vulnerability in Jenkins Docker Plugin 1.1.6 and earlier in DockerAPI.DescriptorImpl#doTestConnection allowed users with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. |
| CVE-2018-15664 | High | 2019-05-23 | Not applicable | No public exploit | In Docker through 18.06.1-ce-rc2, the API endpoints behind the 'docker cp' command are vulnerable to a symlink-exchange attack with Directory Traversal, giving attackers arbitrary read-write access to the host filesystem with root privileges, because daemon/archive.go does not do archive operations on a frozen filesystem (or from within a chroot). |
| CVE-2019-5021 | Critical | 2019-05-08 | Not applicable | No public exploit | Versions of the Official Alpine Linux Docker images (since v3.3) contain a NULL password for the `root` user. This vulnerability appears to be the result of a regression introduced in December of 2015. Due to the nature of this issue, systems deployed using affected versions of the Alpine Linux container which utilize Linux PAM, or some other mechanism which uses the system shadow file as an authentication database, may accept a NULL password for the `root` user. |
| CVE-2019-1003065 | High | 2019-04-04 | No exploit published | No public exploit | Jenkins CloudShare Docker-Machine Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system. |
| CVE-2019-5736 | High | 2019-02-11 | Outside Waratek scope | Exploited | runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe. |
| CVE-2018-15514 | High | 2018-09-01 | Not applicable | No public exploit | HandleRequestAsync in Docker for Windows before 18.06.0-ce-rc3-win68 (edge) and before 18.06.0-ce-win72 (stable) deserialized requests over the \\.\pipe\dockerBackend named pipe without verifying the validity of the deserialized .NET objects. This would allow a malicious user in the "docker-users" group (who may not otherwise have administrator access) to escalate to administrator privileges. |
| CVE-2018-10892 | Medium | 2018-07-06 | Not applicable | No public exploit | The default OCI linux spec in oci/defaults{_linux}.go in Docker/Moby from 1.11 to current does not block /proc/acpi pathnames. The flaw allows an attacker to modify host's hardware like enabling/disabling bluetooth or turning up/down keyboard brightness. |
| CVE-2014-5282 | High | 2018-02-06 | Not applicable | No public exploit | Docker before 1.3 does not properly validate image IDs, which allows remote attackers to redirect to another image through the loading of untrusted images via 'docker load'. |
| CVE-2014-5280 | High | 2018-02-06 | Not applicable | No public exploit | boot2docker 1.2 and earlier allows attackers to conduct cross-site request forgery (CSRF) attacks by leveraging Docker daemons enabling TCP connections without TLS authentication. |
| CVE-2014-5279 | High | 2018-02-06 | Not applicable | No public exploit | The Docker daemon managed by boot2docker 1.2 and earlier improperly enables unauthenticated TCP connections by default, which makes it easier for remote attackers to gain privileges or execute arbitrary code from children containers. |
| CVE-2017-14992 | Medium | 2017-11-01 | Not applicable | No public exploit | 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. |
| CVE-2014-0047 | High | 2017-10-06 | Not applicable | No public exploit | Docker before 1.5 allows local users to have unspecified impact via vectors involving unsafe /tmp usage. |
| CVE-2017-1000094 | Medium | 2017-10-05 | No exploit published | No public exploit | Docker Commons Plugin provides a list of applicable credential IDs to allow users configuring a job to select the one they'd like to use to authenticate with a Docker Registry. This functionality did not check permissions, allowing any user with Overall/Read permission to get a list of valid credentials IDs. Those could be used as part of an attack to capture the credentials using another vulnerability. |
| CVE-2017-11468 | High | 2017-07-20 | Not applicable | No public exploit | Docker Registry before 2.6.2 in Docker Distribution does not properly restrict the amount of content accepted from a user, which allows remote attackers to cause a denial of service (memory consumption) via the manifest endpoint. |
| CVE-2016-9962 | Medium | 2017-01-31 | Not applicable | No public exploit | 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. |
| CVE-2016-7569 | Medium | 2017-01-27 | Not applicable | No public exploit | Directory traversal vulnerability in docker2aci before 0.13.0 allows remote attackers to write to arbitrary files via a .. (dot dot) in the embedded layer data in an image. |
| CVE-2016-6595 | Medium | 2017-01-04 | Not applicable | No public exploit | The SwarmKit toolkit 1.12.0 for Docker allows remote authenticated users to cause a denial of service (prevention of cluster joins) via a long sequence of join and quit actions. NOTE: the vendor disputes this issue, stating that this sequence is not "removing the state that is left by old nodes. At some point the manager obviously stops being able to accept new nodes, since it runs out of memory. Given that both for Docker swarm and for Docker Swarmkit nodes are *required* to provide a secret token (it's actually the only mode of operation), this means that no adversary can simply join nodes and exhaust manager resources. We can't do anything about a manager running out of memory and not being able to add new legitimate nodes to the system. This is merely a resource provisioning issue, and definitely not a CVE worthy vulnerability. |
| CVE-2016-8867 | High | 2016-10-28 | Not applicable | No public exploit | Docker Engine 1.12.2 enabled ambient capabilities with misconfigured capability policies. This allowed malicious images to bypass user permissions to access files within the container filesystem or mounted volumes. |
| CVE-2016-8579 | Medium | 2016-10-28 | Not applicable | No public exploit | docker2aci <= 0.12.3 has an infinite loop when handling local images with cyclic dependency chain. |
| CVE-2016-3697 | High | 2016-06-01 | Not applicable | No public exploit | libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container. |
| CVE-2015-3631 | Low | 2015-05-18 | Not applicable | No public exploit | Docker Engine before 1.6.1 allows local users to set arbitrary Linux Security Modules (LSM) and docker_t policies via an image that allows volumes to override files in /proc. |
| CVE-2015-3630 | High | 2015-05-18 | Not applicable | No public exploit | Docker Engine before 1.6.1 uses weak permissions for (1) /proc/asound, (2) /proc/timer_stats, (3) /proc/latency_stats, and (4) /proc/fs, which allows local users to modify the host, obtain sensitive information, and perform protocol downgrade attacks via a crafted image. |
| CVE-2015-3627 | High | 2015-05-18 | Not applicable | No public exploit | Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a symlink attack in an image. |
| CVE-2015-1843 | Medium | 2015-04-06 | Not applicable | No public exploit | The Red Hat docker package before 1.5.0-28, when using the --add-registry option, falls 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. NOTE: this vulnerability exists because of a CVE-2014-5277 regression. |
| CVE-2014-9358 | Medium | 2014-12-16 | Not applicable | No public exploit | Docker before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path traversal attacks and spoof repositories via a crafted image in a (1) "docker load" operation or (2) "registry communications." |
| CVE-2014-9357 | High | 2014-12-16 | Not applicable | No public exploit | Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build in a Dockerfile in an LZMA (.xz) archive, related to the chroot for archive extraction. |
| CVE-2014-6408 | Medium | 2014-12-12 | Not applicable | No public exploit | Docker 1.3.0 through 1.3.1 allows remote attackers to modify the default run profile of image containers and possibly bypass the container by applying unspecified security options to an image. |
| CVE-2014-6407 | High | 2014-12-12 | Not applicable | No public exploit | Docker before 1.3.2 allows remote attackers to write to arbitrary files and execute arbitrary code via a (1) symlink or (2) hard link attack in an image archive in a (a) pull or (b) load operation. |
| CVE-2014-5277 | Medium | 2014-11-17 | Not applicable | No public exploit | 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. |
| CVE-2014-3499 | High | 2014-07-11 | Not applicable | No public exploit | Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors. |
| CVE-2004-2197 | High | 2004-12-31 | Not applicable | No public exploit | kdocker.cpp in kdocker 0.1 through 0.8 does not properly check the ownership of files, which could allow local users to execute arbitrary programs. |