NetSight

Security Dashboard

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

Reset
905 matching advisories · page 10 of 31Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2024-5460 A vulnerability in the default configuration of the Simple Network Management Protocol (SNMP) feature of Brocade Fabric OS versions before v9.0.0 could allow a… broadcom · fabric_operating_system 2024-06-26 medium5.9 CVE-2024-29954 A vulnerability in a password management API in Brocade Fabric OS versions before v9.2.1, v9.2.0b, v9.1.1d, and v8.2.3e prints sensitive information in log fil… broadcom · fabric_operating_system 2024-06-26 medium4.3 CVE-2024-29953 A vulnerability in the web interface in Brocade Fabric OS before v9.2.1, v9.2.0b, and v9.1.1d prints encoded session passwords on session storage for Virtual F… broadcom · fabric_operating_system 2024-06-26 critical9.8 CVE-2024-37079 Broadcom VMware vCenter Server Out-of-bounds Write VulnerabilityExploited vmware · cloud_foundation, vmware · vcenter_server 2024-06-18 high7.8 CVE-2024-2860 The PostgreSQL implementation in Brocade SANnav versions before 2.3.0a is vulnerable to an incorrect local authentication flaw. broadcom · brocade_sannav 2024-05-08 medium6.8 CVE-2024-2859 By default, SANnav OVA is shipped with root user login enabled. broadcom · brocade_sannav 2024-04-27 high7.6 CVE-2024-4173 A vulnerability in Brocade SANnav exposes Kafka in the wan interface. broadcom · brocade_sannav 2024-04-25 high8.6 CVE-2024-4161 In Brocade SANnav, before Brocade SANnav v2.3.0, syslog traffic received clear text. broadcom · brocade_sannav 2024-04-25 medium4.3 CVE-2024-4159 Brocade SANnav before v2.3.0a lacks protection mechanisms on port 2377/TCP and 7946/TCP, which could allow an unauthenticated attacker to sniff the SANnav Dock… broadcom · brocade_sannav 2024-04-25 high7.5 CVE-2024-29969 When a Brocade SANnav installation is upgraded from Brocade SANnav v2.2.2 to Brocade SANnav 2.3.0, TLS/SSL weak message authentication code ciphers are added b… broadcom · brocade_sannav 2024-04-19 high7.7 CVE-2024-29968 An information disclosure vulnerability exists in Brocade SANnav before v2.3.1 and v2.3.0a when Brocade SANnav instances are configured in disaster recovery mo… broadcom · brocade_sannav 2024-04-19 medium4.4 CVE-2024-29967 In Brocade SANnav before Brocade SANnav v2.31 and v2.3.0a, it was observed that Docker instances inside the appliance have insecure mount points, allowing read… broadcom · brocade_sannav 2024-04-19 high7.5 CVE-2024-29966 Brocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation that appear as the appliance's root password. broadcom · brocade_sannav 2024-04-19 medium6.8 CVE-2024-29965 In Brocade SANnav before v2.3.1, and v2.3.0a, it is possible to back up the appliance from the web interface or the command line interface ("SSH"). broadcom · brocade_sannav 2024-04-19 medium5.7 CVE-2024-29964 Brocade SANnav versions before v2.3.0a do not correctly set permissions on files, including docker files. broadcom · brocade_sannav 2024-04-19 medium5.5 CVE-2024-29962 Brocade SANnav OVA before v2.3.1 and v2.3.0a have an insecure file permission setting that makes files world-readable. broadcom · brocade_sannav 2024-04-19 low1.9 CVE-2024-29963 Brocade SANnav OVA before v2.3.1, and v2.3.0a, contain hardcoded TLS keys used by Docker. broadcom · brocade_sannav 2024-04-19 high8.2 CVE-2024-29961 A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. broadcom · brocade_sannav 2024-04-19 medium6.8 CVE-2024-29960 In Brocade SANnav server before v2.3.1 and v2.3.0a, the SSH keys inside the OVA image are identical in the VM every time SANnav is installed. broadcom · brocade_sannav 2024-04-19 high8.6 CVE-2024-29959 A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints Brocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support sa… broadcom · brocade_sannav 2024-04-19 high7.5 CVE-2024-29958 A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the encryption key in the console when a privileged user executes the script to replace the … broadcom · brocade_sannav 2024-04-19 high7.5 CVE-2024-29957 When Brocade SANnav before v2.3.1 and v2.3.0a servers are configured in Disaster Recovery mode, the encryption key is stored in the DR log files. broadcom · brocade_sannav 2024-04-19 medium6.5 CVE-2024-29956 A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the Brocade SANnav password in clear text in supportsave logs when a user schedules a switch… broadcom · brocade_sannav 2024-04-18 medium5.0 CVE-2024-29955 A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow a privileged user to print the SANnav encrypted key in PostgreSQL startup logs. broadcom · brocade_sannav 2024-04-17 medium5.5 CVE-2024-29952 A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow an authenticated user to print the Auth, Priv, and SSL key store passwords in unencrypt… broadcom · brocade_sannav 2024-04-17 medium5.7 CVE-2024-29951 Brocade SANnav before v2.3.1 and v2.3.0a uses the SHA-1 hash in internal SSH ports that are not open to remote connection. broadcom · brocade_sannav 2024-04-17 high7.5 CVE-2024-29950 The class FileTransfer implemented in Brocade SANnav before v2.3.1, v2.3.0a, uses the ssh-rsa signature scheme, which has a SHA-1 hash. broadcom · brocade_sannav 2024-04-17 medium4.3 CVE-2023-5973 Brocade Web Interface in Brocade Fabric OS v9.x and before v9.2.0 does not properly represent the portName to the user if the portName contains reserved charac… broadcom · fabric_operating_system 2024-04-05 medium6.3 CVE-2024-24795 HTTP Response splitting in multiple modules in Apache HTTP Server allows an attacker that can inject malicious response headers into backend applications to ca… apache · http_server, debian · debian_linux, fedoraproject · fedora +4 2024-04-04 high7.3 CVE-2023-38709 Faulty input validation in the core of Apache allows malicious or exploitable backend/content generators to split HTTP responses. apache · http_server, debian · debian_linux, fedoraproject · fedora +4 2024-04-04

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.