NetSight

Security Dashboard

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

Reset
526 matching advisories · page 9 of 18Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low2.6 CVE-2024-42177 HCL MyXalytics is affected by SSL∕TLS Protocol affected with BREACH & LUCKY13 vulnerabilities. hcltech · dryice_myxalytics 2025-04-17 high8.1 CVE-2024-42193 HCL BigFix Web Reports' service communicates over HTTPS but exhibits a weakness in its handling of SSL certificate validation. hcltech · bigfix_platform 2025-04-15 medium5.4 CVE-2024-42200 HCL BigFix Web Reports might be subject to a Stored Cross-Site Scripting (XSS) attack, due to a potentially weak validation of user input. hcltech · bigfix_platform 2025-04-15 medium6.5 CVE-2024-42189 HCL BigFix Web Reports might be subject to a Denial of Service (DoS) attack, due to a potentially weak validation of an API parameter. hcltech · bigfix_platform 2025-04-15 low3.5 CVE-2024-42208 HCL Connections is vulnerable to an information disclosure vulnerability which could allow a user to obtain sensitive information they are not entitled to, cau… hcltech · connections 2025-04-04 medium4.3 CVE-2025-0279 HCL Traveler generates some error messages that provide detailed information about errors and failures, such as internal paths, file names, sensitive tokens, c… hcltech · traveler 2025-04-03 medium4.3 CVE-2025-0278 HCL Traveler is affected by an internal path disclosure in a Windows application when the application inadvertently reveals internal file paths, in error messa… hcltech · traveler 2025-04-03 medium5.4 CVE-2025-0272 HCL DevOps Deploy / HCL Launch is vulnerable to HTML injection. hcltechsw · hcl_devops_deploy, hcltechsw · hcl_launch 2025-04-03 medium6.3 CVE-2025-0257 HCL DevOps Deploy / HCL Launch could allow unauthorized access to other services or potential exposure of sensitive data due to missing authentication in its A… hcltechsw · hcl_devops_deploy, hcltechsw · hcl_launch 2025-04-02 medium5.5 CVE-2025-0273 HCL DevOps Deploy / HCL Launch stores potentially sensitive authentication token information in log files that could be read by a local user. hcltechsw · hcl_devops_deploy, hcltechsw · hcl_launch 2025-03-27 medium5.5 CVE-2024-30155 HCL SX does not set the secure attribute on authorization tokens or session cookies. hcltech · hcl_sx 2025-03-26 high7.2 CVE-2025-0255 HCL DevOps Deploy / HCL Launch could allow a remote privileged authenticated attacker to execute arbitrary commands on the system by sending specially crafted … hcltechsw · hcl_devops_deploy, hcltechsw · hcl_launch 2025-03-24 medium4.3 CVE-2025-0256 HCL DevOps Deploy / HCL Launch could allow an authenticated user to obtain sensitive information about other users on the system due to missing authorization f… hcltechsw · hcl_devops_deploy, hcltechsw · hcl_launch 2025-03-24 low2.6 CVE-2024-42176 HCL MyXalytics is affected by concurrent login vulnerability. hcltech · dryice_myxalytics 2025-03-19 medium5.3 CVE-2024-30154 HCL SX is vulnerable to cross-site request forgery vulnerability which could allow an attacker to execute malicious and unauthorized actions transmitted from a… hcltech · hcl_sx 2025-03-03 medium5.3 CVE-2024-30150 HCL MyCloud is affected by Improper Access Control - an unauthenticated privilege escalation vulnerability which may lead to information disclosure and potenti… hcltech · dryice_mycloud 2025-02-25 low3.9 CVE-2024-23563 HCL Connections Docs is vulnerable to a sensitive information disclosure which could allow a user to obtain sensitive information they are not entitled to, cau… hcltech · connections_docs 2025-02-12 medium5.5 CVE-2024-42207 HCL iAutomate is affected by a session fixation vulnerability. hcltech · dryice_iautomate 2025-02-05 medium4.0 CVE-2024-22349 IBM DevOps Velocity 5.0.0 and IBM UrbanCode Velocity 4.0.0 through 4.0. hcltech · devops_velocity, ibm · urbancode_velocity 2025-01-20 medium5.3 CVE-2024-22348 IBM DevOps Velocity 5.0.0 and IBM UrbanCode Velocity 4.0.0 through 4.0. hcltech · devops_velocity, ibm · urbancode_velocity 2025-01-20 medium5.9 CVE-2024-22347 IBM DevOps Velocity 5.0.0 and IBM UrbanCode Velocity 4.0.0 through 4.0. hcltech · devops_velocity, ibm · urbancode_velocity 2025-01-20 low1.6 CVE-2024-42181 HCL MyXalytics is affected by a cleartext transmission of sensitive information vulnerability. hcltech · dryice_myxalytics 2025-01-12 low1.6 CVE-2024-42180 HCL MyXalytics is affected by a malicious file upload vulnerability. hcltech · dryice_myxalytics 2025-01-12 low2.0 CVE-2024-42179 HCL MyXalytics is affected by sensitive information disclosure vulnerability. hcltech · dryice_myxalytics 2025-01-12 low2.6 CVE-2024-42175 HCL MyXalytics is affected by a weak input validation vulnerability. hcltech · dryice_myxalytics 2025-01-11 low3.7 CVE-2024-42174 HCL MyXalytics is affected by username enumeration vulnerability. hcltech · dryice_myxalytics 2025-01-11 medium4.8 CVE-2024-42173 HCL MyXalytics is affected by an improper password policy implementation vulnerability. hcltech · dryice_myxalytics 2025-01-11 medium5.3 CVE-2024-42172 HCL MyXalytics is affected by broken authentication. hcltech · dryice_myxalytics 2025-01-11 medium6.4 CVE-2024-42171 HCL MyXalytics is affected by a session fixation vulnerability. hcltech · dryice_myxalytics 2025-01-11 medium6.8 CVE-2024-42170 HCL MyXalytics is affected by a session fixation vulnerability. hcltech · dryice_myxalytics 2025-01-11

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.