NetSight

Security Dashboard

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

Reset
359 matching advisories · page 5 of 12Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.9 CVE-2025-22245 VMware NSX contains a stored Cross-Site Scripting (XSS) vulnerability in the router port due to improper input validation. broadcom · vmware_nsx, vmware · cloud_foundation, vmware · telco_cloud_infrastructure +1 2025-06-04 medium6.9 CVE-2025-22244 VMware NSX contains a stored Cross-Site Scripting (XSS) vulnerability in the gateway firewall due to improper input validation. broadcom · vmware_nsx, vmware · cloud_foundation, vmware · telco_cloud_infrastructure +1 2025-06-04 medium6.5 CVE-2025-3599 Symantec Endpoint Protection Windows Agent, running an ERASER Engine prior to 119.1.7.8, may be susceptible to an Elevation of Privilege vulnerability, which m… broadcom · symantec_eraser_engine 2025-04-30 medium6.7 CVE-2025-1976 Broadcom Brocade Fabric OS Code Injection VulnerabilityExploited broadcom · fabric_operating_system 2025-04-24 medium5.5 CVE-2022-49459 In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/broadcom: Fix potential NULL dereference in sr_thermal_probe platform_get_r… linux · linux_kernel 2025-02-26 medium5.3 CVE-2024-10405 Brocade SANnav before SANnav 2.3.1b enables weak TLS ciphers on ports 443 and 18082. broadcom · brocade_sannav 2025-02-15 medium4.9 CVE-2025-1053 Under certain error conditions at time of SANnav installation or upgrade, the encryption key can be written into and obtained from a Brocade SANnav supportsave. broadcom · brocade_sannav 2025-02-14 medium5.5 CVE-2024-10404 CalInvocationHandler in Brocade SANnav before 2.3.1b logs sensitive information in clear text. broadcom · brocade_sannav 2025-02-14 medium5.7 CVE-2022-43937 Possible information exposure through log file vulnerability where sensitive fields are recorded in the debug-enabled logs when debugging is turned on in Broca… broadcom · brocade_sannav 2024-11-21 medium6.8 CVE-2022-43936 Brocade SANnav versions before 2.2.2 log Brocade Fabric OS switch passwords when debugging is enabled. broadcom · brocade_sannav 2024-11-21 medium5.3 CVE-2022-43935 An information exposure through log file vulnerability exists in Brocade SANnav before Brocade SANnav 2.2.2, where Brocade Fabric OS Switch passwords and autho… broadcom · brocade_sannav 2024-11-21 medium6.5 CVE-2022-43934 Brocade SANnav before Brocade SANnav 2.2.2 supports key exchange algorithms, which are considered weak on ports 24, 6514, 18023, 19094, and 19095. broadcom · brocade_sannav 2024-11-21 medium4.4 CVE-2022-43933 An information exposure through log file vulnerability exists in Brocade SANnav before Brocade SANnav 2.2.2, where configuration secrets are logged in supports… broadcom · brocade_sannav 2024-11-21 medium5.5 CVE-2020-10369 Certain Cypress (and Broadcom) Wireless Combo chips, when a January 2021 firmware update is not present, allow inferences about memory content via a "Spectra" … 2024-11-10 medium5.5 CVE-2020-10367 Certain Cypress (and Broadcom) Wireless Combo chips, when a January 2021 firmware update is not present, allow memory access via a "Spectra" attack. 2024-11-10 medium6.1 CVE-2024-38493 A reflected cross-site scripting (XSS) vulnerability exists in the PAM UI web interface. broadcom · symantec_privileged_access_management 2024-07-15 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 medium6.8 CVE-2024-2859 By default, SANnav OVA is shipped with root user login enabled. broadcom · brocade_sannav 2024-04-27 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 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 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 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 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 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

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.