NetSight

Security Dashboard

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

Reset
58 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2024-33687 Insufficient verification of data authenticity issue exists in NJ Series CPU Unit all versions and NX Series CPU Unit all versions. omron · nj101-1000_firmware, omron · nj101-1020_firmware, omron · nj101-9000_firmware +9 2024-06-24 high7.8 CVE-2022-45792 Project files may contain malicious contents which the software will use to create files on the filesystem. omron · sysmac_studio 2024-01-22 high8.6 CVE-2022-45790 The Omron FINS protocol has an authenticated feature to prevent access to memory regions. omron · cj1g-cpu45p_firmware, omron · cj1g-cpu45p-gtc_firmware, omron · cj1g-cpu44p_firmware +9 2024-01-22 high8.6 CVE-2022-45794 An attacker with network access to the affected PLC (CJ-series and CS-series PLCs, all versions) may use a network protocol to read and write files on the PLC … omron · sysmac_cj2h-cpu64-eip_firmware, omron · sysmac_cj2h-cpu64_firmware, omron · sysmac_cj2h-cpu65-eip_firmware +9 2024-01-10 high7.8 CVE-2023-22277 Use after free vulnerability exists in CX-Programmer Ver.9.79 and earlier. omron · cx-programmer 2023-08-03 high7.8 CVE-2023-22317 Use after free vulnerability exists in CX-Programmer Ver.9.79 and earlier. omron · cx-programmer 2023-08-03 high7.8 CVE-2023-22314 Use after free vulnerability exists in CX-Programmer Ver.9.79 and earlier. omron · cx-programmer 2023-08-03 high7.8 CVE-2023-38748 Use after free vulnerability exists in CX-Programmer Included in CX-One CXONE-AL[][]D-V4 V9.80 and earlier. omron · cx-programmer 2023-08-03 high7.8 CVE-2023-38747 Heap-based buffer overflow vulnerability exists in CX-Programmer Included in CX-One CXONE-AL[][]D-V4 V9.80 and earlier. omron · cx-programmer 2023-08-03 high7.8 CVE-2023-38746 Out-of-bounds read vulnerability/issue exists in CX-Programmer Included in CX-One CXONE-AL[][]D-V4 V9.80 and earlier. omron · cx-programmer 2023-08-03 high7.5 CVE-2023-38744 Denial-of-service (DoS) vulnerability due to improper validation of specified type of input issue exists in the built-in EtherNet/IP port of the CJ Series CJ2 … omron · cj2m-cpu35_firmware, omron · cj2m-cpu34_firmware, omron · cj2m-cpu33_firmware +9 2023-08-03 high7.8 CVE-2023-27385 Heap-based buffer overflow vulnerability exists in CX-Drive All models all versions. omron · cx-drive 2023-05-10 high7.8 CVE-2023-22366 CX-Motion-MCH v2.32 and earlier contains an access of uninitialized pointer vulnerability. omron · cx-motion-mch_firmware 2023-01-17 high7.8 CVE-2022-46282 Use after free vulnerability in CX-Drive V3.00 and earlier allows a local attacker to execute arbitrary code by having a user to open a specially crafted file, omron · cx-drive 2022-12-21 high7.8 CVE-2022-43667 Stack-based buffer overflow vulnerability exists in CX-Programmer v.9.77 and earlier, which may lead to information disclosure and/or arbitrary code execution … omron · cx-programmer 2022-12-07 high7.8 CVE-2022-43509 Out-of-bounds write vulnerability exists in CX-Programmer v.9.77 and earlier, which may lead to information disclosure and/or arbitrary code execution by havin… omron · cx-programmer 2022-12-07 high7.8 CVE-2022-43508 Use-after free vulnerability exists in CX-Programmer v.9.77 and earlier, which may lead to information disclosure and/or arbitrary code execution by having a u… omron · cx-programmer 2022-12-07 high7.8 CVE-2022-3398 OMRON CX-Programmer 9.78 and prior is vulnerable to an Out-of-Bounds Write, which may allow an attacker to execute arbitrary code. omron · cx-programmer 2022-10-06 high7.8 CVE-2022-3397 OMRON CX-Programmer 9.78 and prior is vulnerable to an Out-of-Bounds Write, which may allow an attacker to execute arbitrary code. omron · cx-programmer 2022-10-06 high7.8 CVE-2022-3396 OMRON CX-Programmer 9.78 and prior is vulnerable to an Out-of-Bounds Write, which may allow an attacker to execute arbitrary code. omron · cx-programmer 2022-10-06 high7.8 CVE-2022-2979 Opening a specially crafted file could cause the affected product to fail to release its memory reference potentially resulting in arbitrary code execution. omron · cx-programmer 2022-09-12 high7.5 CVE-2022-31205 In Omron CS series, CJ series, and CP series PLCs through 2022-05-18, the password for access to the Web UI is stored in memory area D1449...D1452 and can be r… omron · sysmac_cs1_firmware, omron · sysmac_cj2m_firmware, omron · sysmac_cj2h_firmware +4 2022-07-26 high7.5 CVE-2022-31204 Omron CS series, CJ series, and CP series PLCs through 2022-05-18 use cleartext passwords. omron · sysmac_cs1_firmware, omron · sysmac_cj2m_firmware, omron · sysmac_cj2h_firmware +5 2022-07-26 high8.1 CVE-2022-34151 Use of hard-coded credentials vulnerability exists in Machine automation controller NJ series all models V 1.48 and earlier, Machine automation controller NX7 … omron · nx701-1600_firmware, omron · nx701-1700_firmware, omron · nx701-z700_firmware +9 2022-07-04 high7.5 CVE-2022-33971 Authentication bypass by capture-replay vulnerability exists in Machine automation controller NX7 series all models V1.28 and earlier, Machine automation contr… omron · nx701-1600_firmware, omron · nx701-1700_firmware, omron · nx701-z700_firmware +9 2022-07-04 high8.1 CVE-2022-33208 Authentication bypass by capture-replay vulnerability exists in Machine automation controller NJ series all models V 1.48 and earlier, Machine automation contr… omron · nx701-1600_firmware, omron · nx701-1700_firmware, omron · nx701-z700_firmware +9 2022-07-04 high7.8 CVE-2022-26419 Omron CX-Position (versions 2.5.3 and prior) is vulnerable to multiple stack-based buffer overflow conditions while parsing a specific project file, which may … omron · cx-position 2022-04-01 high7.8 CVE-2022-26417 Omron CX-Position (versions 2.5.3 and prior) is vulnerable to a use after free memory condition while processing a specific project file, which may allow an at… omron · cx-position 2022-04-01 high7.8 CVE-2022-26022 Omron CX-Position (versions 2.5.3 and prior) is vulnerable to an out-of-bounds write while processing a specific project file, which may allow an attacker to e… omron · cx-position 2022-04-01 high7.8 CVE-2022-25959 Omron CX-Position (versions 2.5.3 and prior) is vulnerable to memory corruption while processing a specific project file, which may allow an attacker to execut… omron · cx-position 2022-04-01

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.