NetSight

Security Dashboard

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

Reset
151 matching advisories · page 5 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2020-35193 The official sonarqube docker images before alpine (Alpine specific) contain a blank password for a root user. sonarsource · sonarqube_docker_image 2020-12-16 critical9.8 CVE-2020-35467 The Docker Docs Docker image through 2020-12-14 contains a blank password for the root user. docker · docs 2020-12-15 critical9.8 CVE-2020-35466 The Blackfire Docker image through 2020-12-14 contains a blank password for the root user. blackfire · blackfire_docker_image 2020-12-15 critical9.8 CVE-2020-35464 Version 1.3.0 of the Weave Cloud Agent Docker image contains a blank password for the root user. weave · cloud_agent 2020-12-15 critical9.8 CVE-2020-35463 Version 1.0.0 of the Instana Dynamic APM Docker image contains a blank password for the root user. instana · dynamic_apm 2020-12-15 critical9.8 CVE-2020-35462 Version 3.16.0 of the CoScale agent Docker image contains a blank password for the root user. coscale_agent_project · coscale_agent 2020-12-15 critical9.8 CVE-2020-29591 Versions of the Official registry Docker images through 2.7.0 contain a blank password for the root user. docker · registry 2020-12-11 critical9.8 CVE-2020-29602 The official irssi docker images before 1.1-alpine (Alpine specific) contain a blank password for a root user. irssi · docker_image 2020-12-08 critical9.8 CVE-2020-29601 The official notary docker images before signer-0.6.1-1 contain a blank password for a root user. docker · notary_docker_image 2020-12-08 critical9.8 CVE-2020-29581 The official spiped docker images before 1.5-alpine contain a blank password for a root user. docker · spiped_alpine_docker_image 2020-12-08 critical9.8 CVE-2020-29580 The official storm Docker images before 1.2.1 contain a blank password for a root user. docker · storm_docker_image 2020-12-08 critical9.8 CVE-2020-29579 The official Express Gateway Docker images before 1.14.0 contain a blank password for a root user. express-gateway · express-gateway_docker_image 2020-12-08 critical9.8 CVE-2020-29577 The official znc docker images before 1.7.1-slim contain a blank password for a root user. znc · znc_docker_image 2020-12-08 critical9.8 CVE-2020-29576 The official eggdrop Docker images before 1.8.4rc2 contain a blank password for a root user. eggheads · eggdrop_docker_image 2020-12-08 critical9.8 CVE-2020-29575 The official elixir Docker images before 1.8.0-alpine (Alpine specific) contain a blank password for a root user. docker · elixir_alpine_docker_image 2020-12-08 critical9.8 CVE-2020-29564 The official Consul Docker images 0.7.1 through 1.4.2 contain a blank password for a root user. hashicorp · consul_docker_image 2020-12-08 critical9.8 CVE-2020-29578 The official piwik Docker images before fpm-alpine (Alpine specific) contain a blank password for a root user. matomo · piwik_fpm-alpine_docker_image 2020-12-08 critical9.8 CVE-2020-29389 The official Crux Linux Docker images 3.0 through 3.4 contain a blank password for a root user. docker · crux_linux_docker_image 2020-12-02 critical9.8 CVE-2020-11878 The Jitsi Meet (aka docker-jitsi-meet) stack on Docker before stable-4384-1 uses default passwords (such as passw0rd) for system accounts. jitsi · meet 2020-04-17 critical9.8 CVE-2020-11710 An issue was discovered in docker-kong (for Kong) through 2.0.3. konghq · docker-kong 2020-04-12 critical9.8 CVE-2020-7606 OS Command Injection in docker-compose-remote-api npm · docker-compose-remote-api 2020-03-15 critical9.8 CVE-2014-0048 An issue was found in Docker before 1.6.0. docker · docker, apache · geode 2020-01-02 critical9.8 CVE-2018-20871 In Univa Grid Engine before 8.6.3, when configured for Docker jobs and execd spooling on root_squash, weak file permissions ("other" write access) occur in cer… univa · grid_engine 2019-07-30 critical9.8 CVE-2019-14271 Moby Docker cp broken with debian containers go · github.com/docker/docker 2019-07-29 critical9.8 CVE-2019-5021 Versions of the Official Alpine Linux Docker images (since v3.3) contain a NULL password for the `root` user. gliderlabs · docker-alpine, opensuse · leap, f5 · big-ip_controller 2019-05-08 critical9.8 CVE-2018-11757 In Docker Skeleton Runtime for Apache OpenWhisk, a Docker action inheriting the Docker tag openwhisk/dockerskeleton:1.3.0 (or earlier) may allow an attacker to… apache · openwhisk 2018-07-23 critical9.8 CVE-2018-11756 In PHP Runtime for Apache OpenWhisk, a Docker action inheriting one of the Docker tags openwhisk/action-php-v7.2:1.0.0 or openwhisk/action-php-v7.1:1.0.1 (or e… apache · openwhisk 2018-07-23 critical9.8 CVE-2015-9259 In Docker Notary before 0.1, the checkRoot function in gotuf/client/client.go does not check expiry of root.json files, despite a comment stating that it does. docker · notary 2018-03-31 critical9.8 CVE-2016-8954 IBM dashDB Local uses hard-coded credentials that could allow a remote attacker to gain access to the Docker container or database. ibm · dashdb_local 2017-02-08 critical9.8 CVE-2016-9223 A vulnerability in the Docker Engine configuration of Cisco CloudCenter Orchestrator (CCO; formerly CliQr) could allow an unauthenticated, remote attacker to i… cisco · cloudcenter_orchestrator 2016-12-26

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.