NetSight

Security Dashboard

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

Reset
294 matching advisories · page 3 of 10Index updated 5 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2024-39883 Delta Electronics CNCSoft-G2 lacks proper validation of the length of user-supplied data prior to copying it to a fixed-length heap-based buffer. deltaww · cncsoft-g2 2024-07-09 high8.8 CVE-2024-39882 Delta Electronics CNCSoft-G2 lacks proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. deltaww · cncsoft-g2 2024-07-09 high8.8 CVE-2024-39881 Delta Electronics CNCSoft-G2 lacks proper validation of user-supplied data, which can result in a memory corruption condition. deltaww · cncsoft-g2 2024-07-09 high7.8 CVE-2024-39880 Delta Electronics CNCSoft-G2 lacks proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. deltaww · cncsoft-g2 2024-07-09 high7.5 CVE-2024-4549 A denial of service vulnerability exists in Delta Electronics DIAEnergie v1.10.1.8610 and prior. deltaww · diaenergie 2024-05-06 critical9.8 CVE-2024-4548 An SQLi vulnerability exists in Delta Electronics DIAEnergie v1.10.1.8610 and prior when CEBC.exe processes a 'RecalculateHDMWYC' message, which is split into … deltaww · diaenergie 2024-05-06 critical9.8 CVE-2024-4547 A SQLi vulnerability exists in Delta Electronics DIAEnergie v1.10.1.8610 and prior when CEBC.exe processes a 'RecalculateScript' message, which is splitted int… deltaww · diaenergie 2024-05-06 high8.8 CVE-2024-34033 Delta Electronics DIAEnergie has insufficient input validation which makes it possible to perform a path traversal attack and write outside of the intended dir… deltaww · diaenergie 2024-05-03 high8.8 CVE-2024-34032 Delta Electronics DIAEnergie is vulnerable to an SQL injection vulnerability that exists in the GetDIACloudList endpoint. deltaww · diaenergie 2024-05-03 high8.8 CVE-2024-34031 Delta Electronics DIAEnergie is vulnerable to an SQL injection vulnerability that exists in the script Handler_CFG.ashx. deltaww · diaenergie 2024-05-03 high7.8 CVE-2024-4192 Delta Electronics CNCSoft-G2 lacks proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. deltaww · cncsoft-g2 2024-04-30 high8.8 CVE-2024-25574 SQL injection vulnerability exists in GetDIAE_usListParameters. deltaww · diaenergie 2024-04-01 high8.1 CVE-2024-28171 It is possible to perform a path traversal attack and write outside of the intended directory. deltaww · diaenergie 2024-03-21 medium4.6 CVE-2024-28045 Improper neutralization of input within the affected product could lead to cross-site scripting. deltaww · diaenergie 2024-03-21 high8.8 CVE-2024-28040 SQL injection vulnerability exists in GetDIAE_astListParameters. deltaww · diaenergie 2024-03-21 high8.1 CVE-2024-25567 Path traversal attack is possible and write outside of the intended directory and may access sensitive information. deltaww · diaenergie 2024-03-21 high8.8 CVE-2024-23975 SQL injection vulnerability exists in GetDIAE_slogListParameters. deltaww · diaenergie 2024-03-21 high8.8 CVE-2024-23494 SQL injection vulnerability exists in GetDIAE_unListParameters. deltaww · diaenergie 2024-03-21 high8.8 CVE-2024-28891 SQL injection vulnerability exists in the script Handler_CFG.ashx. deltaww · diaenergie 2024-03-21 high8.8 CVE-2024-28029 Privileges are not fully verified server-side, which can be abused by a user with limited privileges to bypass authorization and access privileged functionalit… deltaww · diaenergie 2024-03-21 high8.8 CVE-2024-25937 SQL injection vulnerability exists in the script DIAE_tagHandler.ashx. deltaww · diaenergie 2024-03-21 high7.8 CVE-2024-1941 Delta Electronics CNCSoft-B versions 1.0.0.4 and prior are vulnerable to a stack-based buffer overflow, which may allow an attacker to execute arbitrary code. deltaww · cncsoft-b 2024-03-01 high7.8 CVE-2024-1595 Delta Electronics CNCSoft-B DOPSoft prior to v4.0.0.82 insecurely loads libraries, which may allow an attacker to use DLL hijacking and take over the system wh… deltaww · cncsoft-b, deltaww · dopsoft 2024-02-29 high8.2 CVE-2023-5131 A heap buffer-overflow exists in Delta Electronics ISPSoft. deltaww · ispsoft 2024-01-18 high8.2 CVE-2023-5130 A buffer overflow vulnerability exists in Delta Electronics WPLSoft. deltaww · wplsoft 2024-01-18 high8.8 CVE-2023-43824 A stack based buffer overflow exists in Delta Electronics Delta Industrial Automation DOPSoft when parsing the wTitleTextLen field of a DPS file. deltaww · dopsoft 2024-01-18 high8.8 CVE-2023-43823 A stack based buffer overflow exists in Delta Electronics Delta Industrial Automation DOPSoft when parsing the wTTitleLen field of a DPS file. deltaww · dopsoft 2024-01-18 high8.8 CVE-2023-43822 A stack based buffer overflow exists in Delta Electronics Delta Industrial Automation DOPSoft when parsing the wLogTitlesTimeLen field of a DPS file. deltaww · dopsoft 2024-01-18 high8.8 CVE-2023-43821 A stack based buffer overflow exists in Delta Electronics Delta Industrial Automation DOPSoft when parsing the wLogTitlesActionLen field of a DPS file. deltaww · dopsoft 2024-01-18 high8.8 CVE-2023-43820 A stack based buffer overflow exists in Delta Electronics Delta Industrial Automation DOPSoft when parsing the wLogTitlesPrevValueLen field of a DPS file. deltaww · dopsoft 2024-01-18

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.