NetSight

Security Dashboard

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

Reset
151 matching advisories · page 4 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.3 CVE-2020-27352 When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as a result systemd will move pr… canonical · snapd, canonical · ubuntu_linux 2024-06-21 critical9.6 CVE-2024-3166 A Cross-Site Scripting (XSS) vulnerability exists in mintplex-labs/anything-llm, affecting both the desktop application version 1.2.0 and the latest version of… mintplexlabs · anythingllm_desktop, mintplexlabs · anythingllm_docker 2024-06-06 critical9.8 CVE-2024-23054 An issue in Plone Docker Official Image 5.2.13 (5221) open-source software that could allow for remote code execution due to a package listed in ++plone++stati… plone · plone_docker_official_image 2024-02-05 critical GHSA-fmwh-q8g7-g7qg Malware in docker-slim-actionMalware npm · docker-slim-action 2023-08-29 critical9.8 CVE-2023-34844 Play With Docker < 0.0.2 has an insecure CAP_SYS_ADMIN privileged mode causing the docker container to escape. play_with_docker_project · play_with_docker 2023-06-29 critical9.8 CVE-2023-1174 This vulnerability exposes a network port in minikube running on macOS with Docker driver that could enable unexpected remote access to the minikube container. kubernetes · minikube 2023-05-24 critical9.1 CVE-2023-27290 Docker based datastores for IBM Instana (IBM Observability with Instana 239-0 through 239-2, 241-0 through 241-2, and 243-0) do not currently require authentic… ibm · observability_with_instana 2023-03-03 critical GHSA-v3ff-w84f-wm98 Malware in mns-core-dockerrMalware npm · mns-core-dockerr 2022-06-20 critical GHSA-r4h4-c6f6-wr75 Malware in eva.io-dockerMalware npm · eva.io-docker 2022-06-20 critical9.8 CVE-2021-34079 Command injection in docker-tester npm · docker-tester 2022-06-02 critical9.8 CVE-2021-45414 A Remote Code Execution (RCE) vulnerability exists in DataRobot through 2021-10-28 because it allows submission of a Docker environment or Java driver. datarobot · datarobot 2022-02-28 critical9.8 CVE-2021-39070 IBM Security Verify Access 10.0.0.0, 10.0.1.0 and 10.0.2.0 with the advanced access control authentication service enabled could allow an attacker to authentic… ibm · security_verify_access, ibm · security_verify_access_docker 2022-02-02 critical9.8 CVE-2022-23126 TeslaMate before 1.25.1 (when using the default Docker configuration) allows attackers to open doors of Tesla vehicles, start Keyless Driving, and interfere wi… teslamate · teslamate 2022-01-24 critical9.0 CVE-2021-23732 OS Command injection in docker-cli-js npm · docker-cli-js 2021-11-22 critical9.8 CVE-2021-37353 Nagios XI Docker Wizard before version 1.1.3 is vulnerable to SSRF due to improper sanitation in table_population.php. nagios · nagios_xi_docker_wizard 2021-08-13 critical9.8 CVE-2021-27886 rakibtg Docker Dashboard before 2021-02-28 allows command injection in backend/utilities/terminal.js via shell metacharacters in the command parameter of an AP… docker_dashboard_project · docker_dashboard 2021-03-02 critical9.8 CVE-2021-3193 Improper access and command validation in the Nagios Docker Config Wizard before 1.1.2, as used in Nagios XI through 5.7, allows an unauthenticated attacker to… nagios · nagios_xi 2021-01-26 critical9.8 CVE-2020-35197 The official memcached docker images before 1.5.11-alpine (Alpine specific) contain a blank password for a root user. docker · memcached_docker_image 2020-12-17 critical9.8 CVE-2020-35196 The official rabbitmq docker images before 3.7.13-beta.1-management-alpine (Alpine specific) contain a blank password for a root user. docker · rabbitmq_docker_image 2020-12-17 critical9.8 CVE-2020-35195 The official haproxy docker images before 1.8.18-alpine (Alpine specific) contain a blank password for a root user. docker · haproxy_docker_image 2020-12-17 critical9.8 CVE-2020-35192 The official vault docker images before 0.11.6 contain a blank password for a root user. hashicorp · vault 2020-12-17 critical9.8 CVE-2020-35191 The official drupal docker images before 8.5.10-fpm-alpine (Alpine specific) contain a blank password for a root user. drupal · drupal_docker_images 2020-12-17 critical9.8 CVE-2020-35190 The official plone Docker images before version of 4.3.18-alpine (Alpine specific) contain a blank password for a root user. plone · plone 2020-12-17 critical9.8 CVE-2020-35186 The official adminer docker images before 4.7.0-fastcgi contain a blank password for a root user. docker · adminer 2020-12-17 critical9.8 CVE-2020-35184 The official composer docker images before 1.8.3 contain a blank password for a root user. docker · composer_docker_image 2020-12-17 critical9.8 CVE-2020-35189 The official kong docker images before 1.0.2-alpine (Alpine specific) contain a blank password for a root user. kong · kong_alpine_docker_image 2020-12-17 critical9.8 CVE-2020-35187 The official telegraf docker images before 1.9.4-alpine (Alpine specific) contain a blank password for a root user. influxdata · telegraf 2020-12-17 critical9.8 CVE-2020-35185 The official ghost docker images before 2.16.1-alpine (Alpine specific) contain a blank password for a root user. docker · ghost_alpine_docker_image 2020-12-17 critical9.8 CVE-2020-35469 The Software AG Terracotta Server OSS Docker image 5.4.1 contains a blank password for the root user. softwareag · terracotta_server_oss 2020-12-16 critical9.8 CVE-2020-35468 The Appbase streams Docker image 2.1.2 contains a blank password for the root user. appbase · streams 2020-12-16

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.