NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
190 matching advisories · page 6 of 7Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2020-14300 The docker packages version docker-1.13.1-108.git4ef4b30.el7 as released for Red Hat Enterprise Linux 7 Extras via RHBA-2020:0053 (https://access.redhat.com/er… docker · docker, redhat · enterprise_linux_server 2020-07-13 high8.8 CVE-2020-14298 The version of docker as released for Red Hat Enterprise Linux 7 Extras via RHBA-2020:0053 advisory included an incorrect version of runc missing the fix for C… docker · docker, redhat · openshift_container_platform, redhat · enterprise_linux_server 2020-07-13 high7.8 CVE-2020-15360 com.docker.vmnetd in Docker Desktop 2.3.0.3 allows privilege escalation because of a lack of client verification. docker · docker_desktop 2020-06-27 high7.8 CVE-2020-11492 An issue was discovered in Docker Desktop through 2.2.0.5 on Windows. docker · docker_desktop 2020-06-05 high8.4 CVE-2019-3682 The docker-kubic package in SUSE CaaS Platform 3.0 before 17.09.1_ce-7.6.1 provided access to an insecure API locally on the Kubernetes master node. suse · caas_platform 2020-01-17 high7.5 CVE-2014-8179 Docker Engine before 1.8.3 and CS Docker Engine before 1.6.2-CS7 does not properly validate and extract the manifest object from its JSON representation during… docker · cs_engine, docker · docker, opensuse · opensuse 2019-12-17 high8.6 CVE-2014-9356 Path Traversal in Docker go · github.com/docker/docker 2019-12-02 high7.5 CVE-2019-16884 Incorrect Authorization in runc go · github.com/opencontainers/runc, go · github.com/opencontainers/selinux 2019-09-25 high7.8 CVE-2019-15752 Docker Desktop Community Edition Privilege Escalation VulnerabilityExploited docker · docker, apache · geode 2019-08-28 high8.4 CVE-2019-13139 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 e… docker · docker 2019-08-22 high7.5 CVE-2019-13509 Secret insertion into debug log in Docker go · github.com/docker/docker 2019-07-18 high8.8 CVE-2019-10340 A cross-site request forgery vulnerability in Jenkins Docker Plugin 1.1.6 and earlier in DockerAPI.DescriptorImpl#doTestConnection allowed users with Overall/R… maven · io.jenkins.docker:docker-plugin 2019-07-11 high7.5 CVE-2018-15664 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… docker · docker 2019-05-23 high8.8 CVE-2019-1003065 Jenkins CloudShare Docker-Machine Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by user… maven · org.jenkins-ci.plugins:cloudshare-docker 2019-04-04 high7.8 CVE-2019-0204 Docker image code execution with Apache Mesos maven · org.apache.mesos:mesos 2019-03-25 high8.6 CVE-2019-5736 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 roo… docker · docker, linuxfoundation · runc, redhat · container_development_kit +9 2019-02-11 high7.5 CVE-2018-3213 Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Docker Images). oracle · weblogic_server 2018-10-17 high7.5 CVE-2018-12608 Docker Authentication Bypass go · github.com/docker/docker 2018-09-10 high7.5 CVE-2018-16398 In Twistlock AuthZ Broker 0.1, regular expressions are mishandled, as demonstrated by containers/aa/pause?aaa=\/start to bypass a policy in which "docker start… twistlock · authz_broker 2018-09-03 high8.8 CVE-2018-15514 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\docker… docker · docker 2018-09-01 high7.8 CVE-2018-9862 util.c in runV 1.0.0 for Docker mishandles a numeric username, which allows attackers to obtain root access by leveraging the presence of an initial numeric va… hyper · runv 2018-04-09 high7.5 CVE-2015-9258 Docker Notary Signature Algorithm Not Matched to Key vulnerability go · github.com/docker/notary 2018-03-31 high8.8 CVE-2018-8059 The Djelibeybi configuration examples for use of NGINX in SUSE Portus 2.3, when applied to certain configurations involving Docker Compose, have a Missing SSL … suse · portus 2018-03-11 high8.1 CVE-2014-5282 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 · docker 2018-02-06 high8.8 CVE-2014-5280 boot2docker 1.2 and earlier allows attackers to conduct cross-site request forgery (CSRF) attacks by leveraging Docker daemons enabling TCP connections without… boot2docker · boot2docker 2018-02-06 high8.8 CVE-2014-5279 The Docker daemon managed by boot2docker 1.2 and earlier improperly enables unauthenticated TCP connections by default, which makes it easier for remote attack… boot2docker · boot2docker 2018-02-06 high7.8 CVE-2014-0047 Docker before 1.5 allows local users to have unspecified impact via vectors involving unsafe /tmp usage. docker · docker 2017-10-06 high7.5 CVE-2017-11468 Docker Registry has Allocation of Resources Without Limits or Throttling go · github.com/docker/distribution 2017-07-20 high7.5 CVE-2017-7669 Apache Hadoop's LinuxContainerExecutor runs docker commands as root with insufficient input validation maven · org.apache.hadoop:hadoop-common 2017-06-05 high8.8 CVE-2017-8928 mailcow 0.14, as used in "mailcow: dockerized" and other products, has CSRF. mailcow · mailcow\ 2017-05-14

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.