NetSight

Security Dashboard

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

Reset
294 matching advisories · page 10 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2019-10951 Delta Industrial Automation CNCSoft, CNCSoft ScreenEditor Version 1.00.88 and prior. deltaww · cncsoft_screeneditor 2019-04-17 medium5.5 CVE-2019-10949 Delta Industrial Automation CNCSoft, CNCSoft ScreenEditor Version 1.00.88 and prior. deltaww · cncsoft_screeneditor 2019-04-17 high7.8 CVE-2019-10947 Delta Industrial Automation CNCSoft, CNCSoft ScreenEditor Version 1.00.88 and prior. deltaww · cncsoft_screeneditor 2019-04-17 medium5.5 CVE-2019-6547 Delta Industrial Automation CNCSoft, CNCSoft ScreenEditor Version 1.00.84 and prior. deltaww · screeneditor 2019-02-28 high7.8 CVE-2018-17929 In Delta Industrial Automation TPEditor, TPEditor Versions 1.90 and prior, multiple stack-based buffer overflow vulnerabilities may be exploited by processing … deltaww · tpeditor 2018-10-11 high7.8 CVE-2018-17927 In Delta Industrial Automation TPEditor, TPEditor Versions 1.90 and prior, multiple out-of-bounds write vulnerabilities may be exploited by processing speciall… deltaww · tpeditor 2018-10-11 high7.8 CVE-2018-14800 Delta Electronics ISPSoft version 3.0.5 and prior allow an attacker, by opening a crafted file, to cause the application to read past the boundary allocated to… deltaww · ispsoft 2018-10-03 medium6.5 CVE-2018-14824 Delta Electronics Delta Industrial Automation PMSoft v2.11 or prior has an out-of-bounds read vulnerability that can be executed when processing project files,… deltaww · delta_industrial_automation_pmsoft 2018-09-27 high8.8 CVE-2018-10636 CNCSoft Version 1.00.83 and prior with ScreenEditor Version 1.00.54 has multiple stack-based buffer overflow vulnerabilities that could cause the software to c… deltaww · cncsoft, deltaww · screeneditor 2018-08-13 high8.1 CVE-2018-10598 CNCSoft Version 1.00.83 and prior with ScreenEditor Version 1.00.54 has two out-of-bounds read vulnerabilities could cause the software to crash due to lacking… deltaww · cncsoft, deltaww · screeneditor 2018-08-13 critical9.8 CVE-2018-10594 Delta Industrial Automation COMMGR from Delta Electronics versions 1.08 and prior with accompanying PLC Simulators (DVPSimulator EH2, EH3, ES2, SE, SS2 and AHS… deltaww · commgr 2018-06-26 critical9.8 CVE-2018-10623 Delta Electronics Delta Industrial Automation DOPSoft version 4.00.04 and prior performs read operations on a memory buffer where the position can be determine… deltaww · delta_industrial_automation_dopsoft 2018-06-18 critical9.8 CVE-2018-10621 Delta Electronics Delta Industrial Automation DOPSoft version 4.00.04 and prior utilizes a fixed-length stack buffer where a value larger than the buffer can b… deltaww · delta_industrial_automation_dopsoft 2018-06-18 critical9.8 CVE-2018-10617 Delta Electronics Delta Industrial Automation DOPSoft version 4.00.04 and prior utilizes a fixed-length heap buffer where a value larger than the buffer can be… deltaww · delta_industrial_automation_dopsoft 2018-06-18 critical9.8 CVE-2018-8871 In Delta Electronics Automation TPEditor version 1.89 or prior, parsing a malformed program file may cause heap-based buffer overflow vulnerability, which may … deltaww · tpeditor 2018-05-25 high8.8 CVE-2018-7509 WPLSoft in Delta Electronics versions 2.45.0 and prior writes data from a file outside the bounds of the intended buffer space, which could cause memory corrup… deltaww · wplsoft 2018-05-04 high8.8 CVE-2018-7507 WPLSoft in Delta Electronics versions 2.45.0 and prior utilizes a fixed length heap buffer where a value larger than the buffer can be read from a file into th… deltaww · wplsoft 2018-05-04 high8.8 CVE-2018-7494 WPLSoft in Delta Electronics versions 2.45.0 and prior utilizes a fixed length stack buffer where a value larger than the buffer can be read from a file into t… deltaww · wplsoft 2018-05-04 high7.8 CVE-2018-8839 Delta PMSoft versions 2.10 and prior have multiple stack-based buffer overflow vulnerabilities where a .ppm file can introduce a value larger than is readable … deltaww · pmsoft 2018-04-30 high7.8 CVE-2018-5476 A Stack-based Buffer Overflow issue was discovered in Delta Electronics Delta Industrial Automation DOPSoft, Version 4.00.01 or prior. deltaww · delta_industrial_automation_dopsoft 2018-03-15 high7.8 CVE-2017-16751 A Stack-based Buffer Overflow issue was discovered in Delta Electronics Delta Industrial Automation Screen Editor, Version 2.00.23.00 or prior. deltaww · delta_industrial_automation_screen_editor 2018-03-15 high7.8 CVE-2017-16749 A Use-after-Free issue was discovered in Delta Electronics Delta Industrial Automation Screen Editor, Version 2.00.23.00 or prior. deltaww · delta_industrial_automation_screen_editor 2018-03-15 high7.8 CVE-2017-16747 An Out-of-bounds Write issue was discovered in Delta Electronics Delta Industrial Automation Screen Editor, Version 2.00.23.00 or prior. deltaww · delta_industrial_automation_screen_editor 2018-03-15 high7.8 CVE-2017-16745 A Type Confusion issue was discovered in Delta Electronics Delta Industrial Automation Screen Editor, Version 2.00.23.00 or prior. deltaww · delta_industrial_automation_screen_editor 2018-03-15

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.