NetSight

Security Dashboard

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

Reset
27 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2024-26314 Improper privilege management in Jungo WinDriver 6.0.0 through 16.1.0 allows local attackers to escalate privileges and execute arbitrary code. jungo · windriver, mitsubishielectric · cpu_module_logging_configuration_tool, mitsubishielectric · cw_configurator +9 2024-07-02 high7.8 CVE-2024-25088 Improper privilege management in Jungo WinDriver before 12.5.1 allows local attackers to escalate privileges and execute arbitrary code. jungo · windriver, mitsubishielectric · cpu_module_logging_configuration_tool, mitsubishielectric · cw_configurator +9 2024-07-02 high7.8 CVE-2024-25086 Improper privilege management in Jungo WinDriver before 12.2.0 allows local attackers to escalate privileges and execute arbitrary code. jungo · windriver, mitsubishielectric · cpu_module_logging_configuration_tool, mitsubishielectric · cw_configurator +9 2024-07-02 high7.8 CVE-2024-22106 Improper privilege management in Jungo WinDriver before 12.5.1 allows local attackers to escalate privileges, execute arbitrary code, or cause a Denial of Serv… jungo · windriver, mitsubishielectric · cpu_module_logging_configuration_tool, mitsubishielectric · cw_configurator +9 2024-07-02 high7.8 CVE-2023-51776 Improper privilege management in Jungo WinDriver before 12.1.0 allows local attackers to escalate privileges and execute arbitrary code. jungo · windriver, mitsubishielectric · cpu_module_logging_configuration_tool, mitsubishielectric · cw_configurator +9 2024-07-02 high7.5 CVE-2023-51787 An issue was discovered in Wind River VxWorks 7 22.09 and 23.03. windriver · vxworks 2024-02-15 high8.8 CVE-2023-38346 An issue was discovered in Wind River VxWorks 6.9 and 7. windriver · vxworks 2023-09-22 high7.5 CVE-2022-38767 An issue was discovered in Wind River VxWorks 6.9 and 7, that allows a specifically crafted packet sent by a Radius server, may cause Denial of Service during … windriver · vxworks 2022-11-25 high7.4 CVE-2021-3450 The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. rust · openssl-src 2021-03-25 high7.3 CVE-2020-28895 In Wind River VxWorks, memory allocator has a possible overflow in calculating the memory block's size to be allocated by calloc(). windriver · vxworks, oracle · communications_eagle 2021-02-03 high7.5 CVE-2020-11440 httpRpmFs in WebCLI in Wind River VxWorks 5.5 through 7 SR0640 has no check for an escape from the web root. windriver · vxworks 2020-07-23 high7.5 CVE-2020-10664 The IGMP component in VxWorks 6.8.3 IPNET CVE patches created in 2019 has a NULL Pointer Dereference. windriver · vxworks 2020-04-27 high7.5 CVE-2019-12258 Wind River VxWorks 6.6 through vx7 has Session Fixation in the TCP component. windriver · vxworks, sonicwall · sonicos, siemens · siprotec_5_firmware +9 2019-08-09 high8.1 CVE-2019-12263 Wind River VxWorks 6.9.4 and vx7 has a Buffer Overflow in the TCP component (issue 4 of 4). windriver · vxworks, sonicwall · sonicos, siemens · siprotec_5_firmware +9 2019-08-09 high7.5 CVE-2019-12259 Wind River VxWorks 6.6, 6.7, 6.8, 6.9 and vx7 has an array index error in the IGMPv3 client component. windriver · vxworks, sonicwall · sonicos, siemens · siprotec_5_firmware +8 2019-08-09 high8.8 CVE-2019-12257 Wind River VxWorks 6.6 through 6.9 has a Buffer Overflow in the DHCP client component. windriver · vxworks, sonicwall · sonicos, siemens · siprotec_5_firmware +7 2019-08-09 high7.1 CVE-2019-12264 Wind River VxWorks 6.6, 6.7, 6.8, 6.9.3, 6.9.4, and Vx7 has Incorrect Access Control in IPv4 assignment by the ipdhcpc DHCP client component. windriver · vxworks, belden · hirschmann_hios, belden · garrettcom_magnum_dx940e_firmware +4 2019-08-05 high8.1 CVE-2019-9865 When RPC is enabled in Wind River VxWorks 6.9 prior to 6.9.1, a specially crafted RPC request can trigger an integer overflow leading to an out-of-bounds memor… windriver · vxworks 2019-05-29 high7.8 CVE-2018-5189 Race condition in Jungo Windriver 12.5.1 allows local users to cause a denial of service (buffer overflow) or gain system privileges by flipping pool buffer si… jungo · windriver 2018-01-11 high7.8 CVE-2017-14344 This vulnerability allows local attackers to escalate privileges on Jungo WinDriver 12.4.0 and earlier. jungo · windriver 2017-09-12 high7.8 CVE-2017-14153 This vulnerability allows local attackers to escalate privileges on Jungo WinDriver 12.4.0 and earlier. jungo · windriver 2017-09-11 high7.8 CVE-2017-14075 This vulnerability allows local attackers to escalate privileges on Jungo WinDriver 12.4.0 and earlier. jungo · windriver 2017-09-11 high8.1 CVE-2015-7599 Integer overflow in the _authenticate function in svc_auth.c in Wind River VxWorks 5.5 through 6.9.4.1, when the Remote Procedure Call (RPC) protocol is enable… windriver · vxworks 2017-02-07 high7.8 CVE-2013-0711 IPSSH (aka the SSH server) in Wind River VxWorks 6.5 through 6.9 allows remote attackers to cause a denial of service (daemon outage) via a crafted authenticat… windriver · vxworks 2013-03-20 high7.8 CVE-2010-2968 The FTP daemon in Wind River VxWorks does not close the TCP connection after a number of failed login attempts, which makes it easier for remote attackers to o… windriver · vxworks 2010-08-05 high7.8 CVE-2010-2967 The loginDefaultEncrypt algorithm in loginLib in Wind River VxWorks before 6.9 does not properly support a large set of distinct possible passwords, which make… windriver · vxworks 2010-08-05 high7.8 CVE-2010-2966 The INCLUDE_SECURITY functionality in Wind River VxWorks 6.x, 5.x, and earlier uses the LOGIN_USER_NAME and LOGIN_USER_PASSWORD (aka LOGIN_PASSWORD) parameters… windriver · vxworks 2010-08-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.