NetSight

Security Dashboard

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

Reset
163 matching advisories · page 4 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.2 CVE-2023-38369 IBM Security Access Manager Container 10.0.0.0 through 10.0.6.1 does not require that docker images should have strong passwords by default, which makes it eas… ibm · security_access_manager_container 2024-02-07 medium6.2 CVE-2023-32329 IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10… ibm · security_verify_access, ibm · security_verify_access_docker 2024-02-03 medium6.5 CVE-2023-31006 IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10… ibm · security_verify_access, ibm · security_verify_access_docker 2024-02-03 medium6.2 CVE-2023-31005 IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10… ibm · security_verify_access, ibm · security_verify_access_docker 2024-02-03 medium4.7 CVE-2024-23824 mailcow is a dockerized email package, with multiple containers linked in one bridged network. mailcow · mailcow\ 2024-02-02 medium6.9 CVE-2024-24557 Classic builder cache poisoning go · github.com/docker/docker, go · github.com/moby/moby 2024-02-01 medium6.1 CVE-2024-23055 An issue in Plone Docker Official Image 5.2.13 (5221) open-source software allows for remote code execution via improper validation of input by the HOST header… plone · plone_docker_official_image 2024-01-25 medium6.2 CVE-2023-38267 IBM Security Access Manager Appliance (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.6.1) could all… ibm · security_verify_access, ibm · security_verify_access_docker 2024-01-11 medium5.1 CVE-2023-31001 IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.6.1) temporari… ibm · security_verify_access, ibm · security_verify_access_docker 2024-01-11 medium6.5 CVE-2023-40453 Docker Machine through 0.16.2 allows an attacker, who has control of a worker node, to provide crafted version data, which might potentially trick an administr… docker · machine 2023-11-07 medium GHSA-jq35-85cj-fj4p /sys/devices/virtual/powercap accessible by default to containers go · github.com/docker/docker, go · github.com/docker/docker, go · github.com/docker/docker 2023-10-30 medium5.4 CVE-2023-45821 Artifact Hub has Incorrect Docker Hub registry check go · github.com/artifacthub/hub 2023-10-19 medium6.7 CVE-2023-0627 Docker Desktop 4.11.x allows --no-windows-containers flag bypass via IPC response spoofing which may lead to Local Privilege Escalation (LPE).This issue affect… docker · docker_desktop 2023-09-25 medium6.8 CVE-2023-39523 ScanCode.io command injection in docker image fetch process pip · scancodeio 2023-08-07 medium6.3 CVE-2022-38730 Docker Desktop for Windows before 4.6 allows attackers to overwrite any file through the windowscontainers/start dockerBackendV2 API by controlling the data-ro… docker · desktop 2023-04-27 medium5.9 CVE-2023-1802 In Docker Desktop 4.17.x the Artifactory Integration falls back to sending registry credentials over plain HTTP if the HTTPS health check has failed. docker · desktop 2023-04-06 medium6.8 CVE-2023-28841 Docker Swarm encrypted overlay network traffic may be unencrypted go · github.com/docker/docker 2023-04-04 medium6.8 CVE-2023-28842 Docker Swarm encrypted overlay network with a single endpoint is unauthenticated go · github.com/docker/docker 2023-04-04 medium6.5 CVE-2023-28109 Authorization Bypass Through User-Controlled Key play-with-docker go · github.com/play-with-docker/play-with-docker 2023-03-16 medium6.1 CVE-2023-0628 Docker Desktop before 4.17.0 allows an attacker to execute an arbitrary command inside a Dev Environments container during initialization by tricking a user to… docker · docker_desktop 2023-03-13 medium6.5 CVE-2022-36775 IBM Security Verify Access 10.0.0.0, 10.0.1.0, 10.0.2.0, 10.0.3.0, and10.0.4.0 is vulnerable to HTTP header injection, caused by improper validation of input b… ibm · security_verify_access, ibm · security_verify_access_docker 2023-02-17 medium6.3 CVE-2022-22984 Snyk plugins vulnerable to Command Injection npm · snyk, npm · snyk-mvn-plugin, npm · snyk-sbt-plugin +5 2022-11-30 medium4.2 CVE-2022-43679 The Docker image of ownCloud Server through 10.11 contains a misconfiguration that renders the trusted_domains config useless. owncloud · owncloud 2022-11-10 medium5.3 CVE-2022-36109 Docker supplementary group permissions not set up properly, allowing attackers to bypass primary group restrictions go · github.com/docker/docker 2022-09-09 medium6.7 CVE-2022-30137 Executive Summary An Elevation of Privilege (EOP) vulnerability has been identified within Service Fabric clusters that run Docker containers. microsoft · service_fabric 2022-06-15 medium GHSA-fx5p-f64h-93xc Opened exploitable ports in default docker-compose.yaml in go-ipfs go · github.com/ipfs/go-ipfs 2022-04-04 medium5.9 CVE-2022-24769 Moby (Docker Engine) started with non-empty inheritable Linux process capabilities go · github.com/moby/moby, go · github.com/docker/docker 2022-03-24 medium5.3 CVE-2022-23774 Docker Desktop before 4.4.4 on Windows allows attackers to move arbitrary files. docker · docker_desktop 2022-02-01 medium5.5 CVE-2021-31821 When the Windows Tentacle docker image starts up it logs all the commands that it runs along with the arguments, which writes the Octopus Server API key in pla… octopus · tentacle 2022-01-19 medium5.5 CVE-2021-45449 Docker Desktop version 4.3.0 and 4.3.1 has a bug that may log sensitive information (access token or password) on the user's machine during login. docker · docker_desktop 2022-01-12

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.