Export limit exceeded: 385091 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (576 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2023-43537 | 1 Qualcomm | 224 Ar8035, Ar8035 Firmware, Csr8811 and 221 more | 2025-08-11 | 6.5 Medium |
| Information disclosure while handling T2LM Action Frame in WLAN Host. | ||||
| CVE-2025-21454 | 1 Qualcomm | 385 315 5g Iot Modem, 315 5g Iot Modem Firmware, 9206 Lte Modem and 382 more | 2025-08-11 | 7.5 High |
| Transient DOS while processing received beacon frame. | ||||
| CVE-2025-21446 | 1 Qualcomm | 481 Ar8035, Ar8035 Firmware, Ar9380 and 478 more | 2025-08-11 | 7.5 High |
| Transient DOS may occur when processing vendor-specific information elements while parsing a WLAN frame for BTM requests. | ||||
| CVE-2024-9029 | 1 Freeimage Project | 1 Freeimage | 2025-08-08 | 7.5 High |
| A flaw was found in the freeimage library. Processing a crafted image can cause a buffer over-read of 1 byte in the read_iptc_profile function in the Source/Metadata/IPTC.cpp file because the size of the profile is not being sanitized, causing a crash in the application linked to the library, resulting in a denial of service. | ||||
| CVE-2023-53159 | 1 Sfackler | 1 Openssl | 2025-08-07 | 4.5 Medium |
| The openssl crate before 0.10.55 for Rust allows an out-of-bounds read via an empty string to X509VerifyParamRef::set_host. | ||||
| CVE-2024-23591 | 1 Lenovo | 2 Thinksystem Sr670 V2, Thinksystem Sr670 V2 Firmware | 2025-07-23 | 2 Low |
| ThinkSystem SR670V2 servers manufactured from approximately June 2021 to July 2023 were left in Manufacturing Mode which could allow an attacker with privileged logical access to the host or physical access to server internals to modify or disable Intel Boot Guard firmware integrity, SPS security, and other SPS configuration setting. The server’s NIST SP 800-193-compliant Platform Firmware Resiliency (PFR) security subsystem significantly mitigates this issue. | ||||
| CVE-2025-1882 | 1 I-drive | 4 I11, I11 Firmware, I12 and 1 more | 2025-07-12 | 5 Medium |
| A vulnerability was found in i-Drive i11 and i12 up to 20250227. It has been rated as critical. Affected by this issue is some unknown functionality of the component Device Setting Handler. The manipulation leads to improper access control for register interface. The attack needs to be done within the local network. The complexity of an attack is rather high. The exploitation is known to be difficult. It was not possible to identify the current maintainer of the product. It must be assumed that the product is end-of-life. | ||||
| CVE-2023-24942 | 1 Microsoft | 13 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 10 more | 2025-07-10 | 7.5 High |
| Remote Procedure Call Runtime Denial of Service Vulnerability | ||||
| CVE-2023-24901 | 1 Microsoft | 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more | 2025-07-10 | 7.5 High |
| Windows NFS Portmapper Information Disclosure Vulnerability | ||||
| CVE-2024-38135 | 1 Microsoft | 4 Windows 11 22h2, Windows 11 23h2, Windows 11 24h2 and 1 more | 2025-07-10 | 7.8 High |
| Windows Resilient File System (ReFS) Elevation of Privilege Vulnerability | ||||
| CVE-2024-38127 | 1 Microsoft | 15 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 12 more | 2025-07-10 | 7.8 High |
| Windows Hyper-V Elevation of Privilege Vulnerability | ||||
| CVE-2024-49031 | 1 Microsoft | 3 365 Apps, Office, Office Long Term Servicing Channel | 2025-07-08 | 7.8 High |
| Microsoft Office Graphics Remote Code Execution Vulnerability | ||||
| CVE-2024-43595 | 1 Microsoft | 1 Edge Chromium | 2025-07-08 | 6.5 Medium |
| Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability | ||||
| CVE-2023-28267 | 1 Microsoft | 14 Remote Desktop Client, Windows 10 1507, Windows 10 1607 and 11 more | 2025-07-07 | 6.5 Medium |
| Remote Desktop Protocol Client Information Disclosure Vulnerability | ||||
| CVE-2023-32002 | 2 Nodejs, Redhat | 4 Node.js, Nodejs, Enterprise Linux and 1 more | 2025-07-02 | 9.8 Critical |
| The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js. | ||||
| CVE-2023-33116 | 1 Qualcomm | 204 Ar8035, Ar8035 Firmware, Ar9380 and 201 more | 2025-06-17 | 7.5 High |
| Transient DOS while parsing ieee80211_parse_mscs_ie in WIN WLAN driver. | ||||
| CVE-2025-47295 | 1 Fortinet | 1 Fortios | 2025-06-04 | 3.4 Low |
| A buffer over-read in Fortinet FortiOS versions 7.4.0 through 7.4.3, versions 7.2.0 through 7.2.7, and versions 7.0.0 through 7.0.14 may allow a remote unauthenticated attacker to crash the FGFM daemon via a specially crafted request, under rare conditions that are outside of the attacker's control. | ||||
| CVE-2023-33040 | 1 Qualcomm | 288 315 5g Iot Modem, 315 5g Iot Modem Firmware, Aqt1000 and 285 more | 2025-06-03 | 7.5 High |
| Transient DOS in Data Modem during DTLS handshake. | ||||
| CVE-2024-38667 | 1 Linux | 1 Linux Kernel | 2025-05-30 | 7.8 High |
| In the Linux kernel, the following vulnerability has been resolved: riscv: prevent pt_regs corruption for secondary idle threads Top of the kernel thread stack should be reserved for pt_regs. However this is not the case for the idle threads of the secondary boot harts. Their stacks overlap with their pt_regs, so both may get corrupted. Similar issue has been fixed for the primary hart, see c7cdd96eca28 ("riscv: prevent stack corruption by reserving task_pt_regs(p) early"). However that fix was not propagated to the secondary harts. The problem has been noticed in some CPU hotplug tests with V enabled. The function smp_callin stored several registers on stack, corrupting top of pt_regs structure including status field. As a result, kernel attempted to save or restore inexistent V context. | ||||
| CVE-2022-2881 | 1 Isc | 1 Bind | 2025-05-28 | 5.5 Medium |
| The underlying bug might cause read past end of the buffer and either read memory it should not read, or crash the process. | ||||