NetSight

Security Dashboard

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

Reset
163 matching advisories · page 5 of 6Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.9 CVE-2021-41091 Moby (Docker Engine) Insufficiently restricted permissions on data directory go · github.com/moby/moby, go · github.com/docker/docker 2021-10-04 medium5.4 CVE-2021-41092 Docker CLI leaks private registry credentials to registry-1.docker.io go · github.com/docker/cli 2021-10-04 medium6.8 CVE-2021-29699 IBM Security Verify Access Docker 10.0.0 could allow a remote priviled user to upload arbitrary files with a dangerous file type that could be excuted by an us… ibm · security_verify_access 2021-07-15 medium6.5 CVE-2021-20537 IBM Security Verify Access Docker 10.0.0 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentica… ibm · security_verify_access 2021-07-15 medium4.8 CVE-2021-20524 IBM Security Verify Access Docker 10.0.0 is vulnerable to cross-site scripting. ibm · security_verify_access 2021-07-15 medium4.9 CVE-2021-20511 IBM Security Verify Access Docker 10.0.0 could allow a remote attacker to traverse directories on the system. ibm · security_verify_access 2021-07-15 medium4.4 CVE-2021-20510 IBM Security Verify Access Docker 10.0.0 stores user credentials in plain clear text which can be read by a local user. ibm · security_verify_access 2021-07-15 medium4.4 CVE-2021-20500 IBM Security Verify Access Docker 10.0.0 could reveal highly sensitive information to a local privileged user. ibm · security_verify_access 2021-07-15 medium5.3 CVE-2021-20498 IBM Security Verify Access Docker 10.0.0 reveals version information in HTTP requests that could be used in further attacks against the system. ibm · security_verify_access 2021-07-15 medium4.9 CVE-2021-20496 IBM Security Verify Access Docker 10.0.0 could allow an authenticated user to bypass input due to improper input validation. ibm · security_verify_access 2021-07-15 medium6.5 CVE-2021-32699 Asymmetric Resource Consumption (Amplification) in Docker containers created by Wings go · github.com/pterodactyl/wings 2021-06-22 medium5.3 CVE-2020-15378 The OVA version of Brocade SANnav before version 2.1.1 installation with IPv6 networking exposes the docker container ports to the network, increasing the pote… broadcom · sannav 2021-06-09 medium5.5 CVE-2021-20191 Insertion of Sensitive Information into Log File in ansible pip · ansible 2021-05-26 medium6.5 CVE-2021-21285 moby docker daemon crash during image pull of malicious image go · github.com/moby/moby 2021-02-02 medium6.8 CVE-2021-21284 moby Access to remapped root allows privilege escalation to real root go · github.com/moby/moby 2021-02-02 medium5.8 CVE-2020-26278 Weave Net is open source software which creates a virtual network that connects Docker containers across multiple hosts and enables their automatic discovery. weave · weave 2021-01-20 medium5.0 CVE-2021-1645 Windows Docker Information Disclosure Vulnerability microsoft · windows_10, microsoft · windows_server_2016, microsoft · windows_server_2019 2021-01-12 medium5.3 CVE-2020-27534 Path Traversal in Moby builder go · github.com/moby/moby, go · github.com/docker/docker 2020-12-30 medium5.9 CVE-2020-26213 Denial-of-Service within Docker container go · ktbs.dev/teler 2020-11-06 medium5.4 CVE-2020-13295 For GitLab Runner before 13.0.12, 13.1.6, 13.2.3, by replacing dockerd with a malicious server, the Shared Runner is susceptible to SSRF. gitlab · runner 2020-08-10 medium6.0 CVE-2020-13401 Improper Input Validation in Docker Engine go · github.com/docker/docker-ce 2020-06-02 medium6.5 CVE-2020-10952 GitLab EE/CE 8.11 through 12.9.1 allows blocked users to pull/push docker images. gitlab · gitlab 2020-03-27 medium6.7 CVE-2020-10665 Docker Desktop allows local privilege escalation to NT AUTHORITY\SYSTEM because it mishandles the collection of diagnostics with Administrator privileges, lead… docker · desktop 2020-03-18 medium5.3 CVE-2014-5278 A vulnerability exists in Docker before 1.2 via container names, which may collide with and override container IDs. docker · docker 2020-02-07 medium5.5 CVE-2014-8178 Docker Engine before 1.8.3 and CS Docker Engine before 1.6.2-CS7 do not use a globally unique identifier to store image layers, which makes it easier for attac… docker · cs_engine, docker · docker, opensuse · opensuse 2019-12-17 medium5.5 CVE-2019-1020014 docker-credential-helpers before 0.6.3 has a double free in the List functions. docker · credential_helpers, fedoraproject · fedora, canonical · ubuntu_linux 2019-07-29 medium4.3 CVE-2019-10342 A missing permission check in Jenkins Docker Plugin 1.1.6 and earlier in various 'fillCredentialsIdItems' methods allowed users with Overall/Read access to enu… maven · io.jenkins.docker:docker-plugin 2019-07-11 medium6.5 CVE-2019-10341 A missing permission check in Jenkins Docker Plugin 1.1.6 and earlier in DockerAPI.DescriptorImpl#doTestConnection allowed users with Overall/Read access to co… maven · io.jenkins.docker:docker-plugin 2019-07-11 medium4.9 CVE-2018-20699 Docker Engine before 18.09 allows attackers to cause a denial of service (dockerd memory consumption) via a large integer in a --cpuset-mems or --cpuset-cpus v… docker · engine, redhat · enterprise_linux_server 2019-01-12 medium5.3 CVE-2018-10892 The default OCI linux spec in oci/defaults{_linux}.go in Docker/Moby from 1.11 to current does not block /proc/acpi pathnames. docker · docker, mobyproject · moby, redhat · openstack +3 2018-07-06

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.