Overview 228 matches · 0 in Waratek scope · 0 protected · 9 exploited · 6 CISA KEV · 6 public PoC · 6 EPSS ≥ 0.5
228matches
0in Waratek scope0.0%
0protected0.0%
9exploited3.9%
6CISA KEV2.6%
6public PoC2.6%
6EPSS ≥ 0.52.6%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
31
13.6%
Not applicable
197
86.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
228
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
9
3.9%
Working exploit published
0
0.0%
Proof of concept only
6
2.6%
Forecast only
0
0.0%
No public exploit
213
93.4%
split by
peak 80 / year
201917
Outside Waratek scope12
Not applicable5
Critical1
High7
Medium9
not blocked17
Proof of concept only1
No public exploit16
202080
Outside Waratek scope9
Not applicable71
Critical6
High25
Medium49
not blocked80
Proof of concept only1
No public exploit79
202124
Outside Waratek scope4
Not applicable20
Critical8
High10
Medium5
Low1
not blocked24
Exploited5
No public exploit19
202229
Outside Waratek scope2
Not applicable27
Critical3
High9
Medium16
Low1
not blocked29
Exploited1
Proof of concept only2
No public exploit26
20239
Not applicable9
High4
Medium4
Low1
not blocked9
No public exploit9
202410
Outside Waratek scope3
Not applicable7
Critical3
High2
Medium5
not blocked10
Exploited1
Proof of concept only2
No public exploit7
202549
Outside Waratek scope1
Not applicable48
Critical3
High40
Medium6
not blocked49
Exploited1
No public exploit48
202610
Not applicable10
High10
not blocked10
Exploited1
No public exploit9
20192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-45059 | High | 2026-04-08 | Not applicable | No public exploit | D-Link DI-8300 v16.07.26A1 was discovered to contain a buffer overflow via the fn parameter in the tgfile_htm function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted input. |
| CVE-2025-45058 | High | 2026-04-08 | Not applicable | No public exploit | D-Link DI-8300 v16.07.26A1 was discovered to contain a buffer overflow via the fx parameter in the jingx_asp function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted input. |
| CVE-2025-45057 | High | 2026-04-08 | Not applicable | No public exploit | D-Link DI-8300 v16.07.26A1 was discovered to contain a buffer overflow via the ip parameter in the ip_position_asp function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted input. |
| CVE-2025-47391 | High | 2026-04-06 | Not applicable | No public exploit | Memory corruption while processing a frame request from user. |
| CVE-2025-47389 | High | 2026-04-06 | Not applicable | No public exploit | Memory corruption when buffer copy operation fails due to integer overflow during attestation report generation. |
| CVE-2026-21385 | High | 2026-03-02 | Not applicable | Exploited | Memory corruption while using alignments for memory allocation. |
| CVE-2025-59600 | High | 2026-03-02 | Not applicable | No public exploit | Memory Corruption when adding user-supplied data without checking available buffer space. |
| CVE-2025-47373 | High | 2026-03-02 | Not applicable | No public exploit | Memory Corruption when accessing buffers with invalid length during TA invocation. |
| CVE-2025-47398 | High | 2026-02-02 | Not applicable | No public exploit | Memory Corruption while deallocating graphics processing unit memory buffers due to improper handling of memory pointers. |
| CVE-2025-47397 | High | 2026-02-02 | Not applicable | No public exploit | Memory Corruption when initiating GPU memory mapping using scatter-gather lists due to unchecked IOMMU mapping errors. |
| CVE-2025-27070 | High | 2025-11-04 | Not applicable | No public exploit | Memory corruption while performing encryption and decryption commands. |
| CVE-2025-27054 | High | 2025-10-09 | Not applicable | No public exploit | Memory corruption while processing a malformed license file during reboot. |
| CVE-2025-27053 | High | 2025-10-09 | Not applicable | No public exploit | Memory corruption during PlayReady APP usecase while processing TA commands. |
| CVE-2025-27032 | High | 2025-09-24 | Not applicable | No public exploit | memory corruption while loading a PIL authenticated VM, when authenticated VM image is loaded without maintaining cache coherency. |
| CVE-2025-21487 | High | 2025-09-24 | Not applicable | No public exploit | Information disclosure while decoding RTP packet received by UE from the network, when payload length mentioned is greater than the available buffer length. |
| CVE-2025-21483 | Critical | 2025-09-24 | Not applicable | No public exploit | Memory corruption when the UE receives an RTP packet from the network, during the reassembly of NALUs. |
| CVE-2025-21481 | High | 2025-09-24 | Not applicable | No public exploit | Memory corruption while performing private key encryption in trusted application. |
| CVE-2025-27066 | High | 2025-08-06 | Not applicable | No public exploit | Transient DOS while processing an ANQP message. |
| CVE-2025-21465 | Medium | 2025-08-06 | Not applicable | No public exploit | Information disclosure while processing the hash segment in an MBN file. |
| CVE-2025-21464 | Medium | 2025-08-06 | Not applicable | No public exploit | Information disclosure while reading data from an image using specified offset and size parameters. |
| CVE-2025-27061 | High | 2025-07-08 | Not applicable | No public exploit | Memory corruption whhile handling the subsystem failure memory during the parsing of video packets received from the video firmware. |
| CVE-2025-27057 | High | 2025-07-08 | Not applicable | No public exploit | Transient DOS while handling beacon frames with invalid IE header length. |
| CVE-2025-27052 | High | 2025-07-08 | Not applicable | No public exploit | Memory corruption while processing data packets in diag received from Unix clients. |
| CVE-2025-27043 | High | 2025-07-08 | Not applicable | No public exploit | Memory corruption while processing manipulated payload in video firmware. |
| CVE-2025-27042 | High | 2025-07-08 | Not applicable | No public exploit | Memory corruption while processing video packets received from video firmware. |
| CVE-2025-21446 | High | 2025-07-08 | Not applicable | No public exploit | Transient DOS may occur when processing vendor-specific information elements while parsing a WLAN frame for BTM requests. |
| CVE-2025-21433 | Medium | 2025-07-08 | Not applicable | No public exploit | Transient DOS when importing a PKCS#8-encoded RSA private key with a zero-sized modulus. |
| CVE-2025-21432 | High | 2025-07-08 | Not applicable | No public exploit | Memory corruption while retrieving the CBOR data from TA. |
| CVE-2025-21427 | High | 2025-07-08 | Not applicable | No public exploit | Information disclosure while decoding this RTP packet Payload when UE receives the RTP packet from the network. |
| CVE-2025-21422 | High | 2025-07-08 | Not applicable | No public exploit | Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses. |
| CVE-2024-53009 | High | 2025-07-08 | Not applicable | No public exploit | Memory corruption while operating the mailbox in Automotive. |
| CVE-2025-21463 | High | 2025-06-03 | Not applicable | No public exploit | Transient DOS while processing the EHT operation IE in the received beacon frame. |
| CVE-2024-53026 | High | 2025-06-03 | Not applicable | No public exploit | Information disclosure when an invalid RTCP packet is received during a VoLTE/VoWiFi IMS call. |
| CVE-2024-53021 | High | 2025-06-03 | Not applicable | No public exploit | Information disclosure may occur while processing goodbye RTCP packet from network. |
| CVE-2024-53020 | High | 2025-06-03 | Not applicable | No public exploit | Information disclosure may occur while decoding the RTP packet with invalid header extension from network. |
| CVE-2025-21468 | High | 2025-05-06 | Not applicable | No public exploit | Memory corruption while reading response from FW, when buffer size is changed by FW while driver is using this size to write null character at the end of buffer. |
| CVE-2025-21459 | High | 2025-05-06 | Not applicable | No public exploit | Transient DOS while parsing per STA profile in ML IE. |
| CVE-2025-21453 | High | 2025-05-06 | Not applicable | No public exploit | Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur. |
| CVE-2024-49845 | High | 2025-05-06 | Not applicable | No public exploit | Memory corruption during the FRS UDS generation process. |
| CVE-2024-49844 | High | 2025-05-06 | Not applicable | No public exploit | Memory corruption while triggering commands in the PlayReady Trusted application. |
| CVE-2024-49842 | High | 2025-05-06 | Not applicable | No public exploit | Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions. |
| CVE-2024-49841 | High | 2025-05-06 | Not applicable | No public exploit | Memory corruption during memory assignment to headless peripheral VM due to incorrect error code handling. |
| CVE-2024-49835 | High | 2025-05-06 | Not applicable | No public exploit | Memory corruption while reading secure file. |
| CVE-2025-21448 | High | 2025-04-07 | Not applicable | No public exploit | Transient DOS may occur while parsing SSID in action frames. |
| CVE-2025-21434 | High | 2025-04-07 | Not applicable | No public exploit | Transient DOS may occur while parsing EHT operation IE or EHT capability IE. |
| CVE-2025-21430 | High | 2025-04-07 | Not applicable | No public exploit | Transient DOS while connecting STA to AP and initiating ADD TS request from AP to establish TSpec session. |
| CVE-2024-45551 | Medium | 2025-04-07 | Not applicable | No public exploit | Cryptographic issue occurs during PIN/password verification using Gatekeeper, where RPMB writes can be dropped on verification failure, potentially leading to a user throttling bypass. |
| CVE-2024-45549 | High | 2025-04-07 | Not applicable | No public exploit | Information disclosure while creating MQ channels. |
| CVE-2024-43065 | High | 2025-04-07 | Not applicable | No public exploit | Cryptographic issues while generating an asymmetric key pair for RKP use cases. |
| CVE-2024-43046 | Medium | 2025-04-07 | Not applicable | No public exploit | There may be information disclosure during memory re-allocation in TZ Secure OS. |
| CVE-2024-33058 | High | 2025-04-07 | Not applicable | No public exploit | Memory corruption while assigning memory from the source DDR memory(HLOS) to ADSP. |
| CVE-2024-53027 | High | 2025-03-03 | Not applicable | No public exploit | Transient DOS may occur while processing the country IE. |
| CVE-2024-53024 | High | 2025-03-03 | Not applicable | No public exploit | Memory corruption in display driver while detaching a device. |
| CVE-2024-49839 | Critical | 2025-02-03 | Not applicable | No public exploit | Memory corruption during management frame processing due to mismatch in T2LM info element. |
| CVE-2024-49838 | High | 2025-02-03 | Not applicable | No public exploit | Information disclosure while parsing the OCI IE with invalid length. |
| CVE-2024-49834 | High | 2025-02-03 | Not applicable | No public exploit | Memory corruption while power-up or power-down sequence of the camera sensor. |
| CVE-2024-45571 | High | 2025-02-03 | Not applicable | No public exploit | Memory corruption may occour occur when stopping the WLAN interface after processing a WMI command from the interface. |
| CVE-2024-45569 | Critical | 2025-02-03 | Not applicable | Exploited | Memory corruption while parsing the ML IE due to invalid frame content. |
| CVE-2024-13176 | Medium | 2025-01-20 | Outside Waratek scope | No public exploit | Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency. There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue. |
| CVE-2024-4741 | Critical | 2024-11-13 | Outside Waratek scope | No public exploit | Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use. The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use. The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use. While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. |
| CVE-2024-44411 | Critical | 2024-09-09 | Not applicable | Proof of concept only | D-Link DI-8300 v16.07.26A1 is vulnerable to command injection via the msp_info_htm function. |
| CVE-2024-44410 | Critical | 2024-09-09 | Not applicable | Proof of concept only | D-Link DI-8300 v16.07.26A1 is vulnerable to command injection via the upgrade_filter_asp function. |
| CVE-2024-6387 | High | 2024-07-01 | Not applicable | Exploited | A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead sshd to handle some signals in an unsafe manner. An unauthenticated, remote attacker may be able to trigger it by failing to authenticate within a set time period. |
| CVE-2024-4603 | Medium | 2024-05-16 | Not applicable | No public exploit | Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks. An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue. |
| CVE-2021-34983 | Medium | 2024-05-07 | Not applicable | No public exploit | NETGEAR Multiple Routers httpd Missing Authentication for Critical Function Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of multiple NETGEAR routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the httpd service, which listens on TCP port 80 by default. The issue results from the lack of authentication prior to allowing access to system configuration information. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-13708. |
| CVE-2021-34982 | High | 2024-05-07 | Not applicable | No public exploit | NETGEAR Multiple Routers httpd Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of multiple NETGEAR routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the httpd service, which listens on TCP port 80 by default. When parsing the strings file, the process does not properly validate the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. . Was ZDI-CAN-13709. |
| CVE-2023-6237 | Medium | 2024-04-25 | Not applicable | No public exploit | Issue summary: Checking excessively long invalid RSA public keys may take a long time. Impact summary: Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service. When function EVP_PKEY_public_check() is called on RSA public keys, a computation is done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more large primes and this computation completes quickly. However, if n is an overly large prime, then this computation would take a long time. An application that calls EVP_PKEY_public_check() and supplies an RSA key obtained from an untrusted source could be vulnerable to a Denial of Service attack. The function EVP_PKEY_public_check() is not called from other OpenSSL functions however it is called from the OpenSSL pkey command line application. For that reason that application is also vulnerable if used with the '-pubin' and '-check' options on untrusted data. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue. |
| CVE-2024-26735 | Medium | 2024-04-03 | Outside Waratek scope | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix possible use-after-free and null-ptr-deref The pernet operations structure for the subsystem must be registered before registering the generic netlink family. |
| CVE-2024-26733 | Medium | 2024-04-03 | Outside Waratek scope | No public exploit | In the Linux kernel, the following vulnerability has been resolved: arp: Prevent overflow in arp_req_get(). syzkaller reported an overflown write in arp_req_get(). [0] When ioctl(SIOCGARP) is issued, arp_req_get() looks up an neighbour entry and copies neigh->ha to struct arpreq.arp_ha.sa_data. The arp_ha here is struct sockaddr, not struct sockaddr_storage, so the sa_data buffer is just 14 bytes. In the splat below, 2 bytes are overflown to the next int field, arp_flags. We initialise the field just after the memcpy(), so it's not a problem. However, when dev->addr_len is greater than 22 (e.g. MAX_ADDR_LEN), arp_netmask is overwritten, which could be set as htonl(0xFFFFFFFFUL) in arp_ioctl() before calling arp_req_get(). To avoid the overflow, let's limit the max length of memcpy(). Note that commit b5f0de6df6dc ("net: dev: Convert sa_data to flexible array in struct sockaddr") just silenced syzkaller. [0]: memcpy: detected field-spanning write (size 16) of single field "r->arp_ha.sa_data" at net/ipv4/arp.c:1128 (size 14) WARNING: CPU: 0 PID: 144638 at net/ipv4/arp.c:1128 arp_req_get+0x411/0x4a0 net/ipv4/arp.c:1128 Modules linked in: CPU: 0 PID: 144638 Comm: syz-executor.4 Not tainted 6.1.74 #31 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-debian-1.16.0-5 04/01/2014 RIP: 0010:arp_req_get+0x411/0x4a0 net/ipv4/arp.c:1128 Code: fd ff ff e8 41 42 de fb b9 0e 00 00 00 4c 89 fe 48 c7 c2 20 6d ab 87 48 c7 c7 80 6d ab 87 c6 05 25 af 72 04 01 e8 5f 8d ad fb <0f> 0b e9 6c fd ff ff e8 13 42 de fb be 03 00 00 00 4c 89 e7 e8 a6 RSP: 0018:ffffc900050b7998 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff88803a815000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff8641a44a RDI: 0000000000000001 RBP: ffffc900050b7a98 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 203a7970636d656d R12: ffff888039c54000 R13: 1ffff92000a16f37 R14: ffff88803a815084 R15: 0000000000000010 FS: 00007f172bf306c0(0000) GS:ffff88805aa00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f172b3569f0 CR3: 0000000057f12005 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> arp_ioctl+0x33f/0x4b0 net/ipv4/arp.c:1261 inet_ioctl+0x314/0x3a0 net/ipv4/af_inet.c:981 sock_do_ioctl+0xdf/0x260 net/socket.c:1204 sock_ioctl+0x3ef/0x650 net/socket.c:1321 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __x64_sys_ioctl+0x18e/0x220 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x37/0x90 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x64/0xce RIP: 0033:0x7f172b262b8d Code: 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f172bf300b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f172b3abf80 RCX: 00007f172b262b8d RDX: 0000000020000000 RSI: 0000000000008954 RDI: 0000000000000003 RBP: 00007f172b2d3493 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f172b3abf80 R15: 00007f172bf10000 </TASK> |
| CVE-2023-25756 | High | 2023-11-14 | Not applicable | No public exploit | Out-of-bounds read in the BIOS firmware for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via adjacent access. |
| CVE-2023-22329 | Low | 2023-11-14 | Not applicable | No public exploit | Improper input validation in the BIOS firmware for some Intel(R) Processors may allow an authenticated user to potentially enable denial of service via adjacent access. |
| CVE-2023-5142 | Medium | 2023-09-24 | Not applicable | No public exploit | A vulnerability classified as problematic was found in H3C GR-1100-P, GR-1108-P, GR-1200W, GR-1800AX, GR-2200, GR-3200, GR-5200, GR-8300, ER2100n, ER2200G2, ER3200G2, ER3260G2, ER5100G2, ER5200G2 and ER6300G2 up to 20230908. This vulnerability affects unknown code of the file /userLogin.asp of the component Config File Handler. The manipulation leads to path traversal. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. VDB-240238 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way. |
| CVE-2022-44611 | High | 2023-08-11 | Not applicable | No public exploit | Improper input validation in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via adjacent access. |
| CVE-2022-43505 | Medium | 2023-08-11 | Not applicable | No public exploit | Insufficient control flow management in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable denial of service via local access. |
| CVE-2022-40982 | Medium | 2023-08-11 | Not applicable | No public exploit | Information exposure through microarchitectural state after transient execution in certain vector execution units for some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access. |
| CVE-2022-38087 | Medium | 2023-05-10 | Not applicable | No public exploit | Exposure of resource to wrong sphere in BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable information disclosure via local access. |
| CVE-2022-33894 | High | 2023-05-10 | Not applicable | No public exploit | Improper input validation in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access. |
| CVE-2023-1077 | High | 2023-03-27 | Not applicable | No public exploit | In the Linux kernel, pick_next_rt_entity() may return a type confused entry, not detected by the BUG_ON condition, as the confused entry will not be NULL, but list_head.The buggy error condition would lead to a type confused entry with the list head,which would then be used as a type confused sched_rt_entity,causing memory corruption. |
| CVE-2022-26047 | Medium | 2022-11-11 | Not applicable | No public exploit | Improper input validation for some Intel(R) PROSet/Wireless WiFi, Intel vPro(R) CSME WiFi and Killer(TM) WiFi products may allow unauthenticated user to potentially enable denial of service via local access. |
| CVE-2022-38132 | High | 2022-08-24 | Not applicable | No public exploit | Command injection vulnerability in Linksys MR8300 router while Registration to DDNS Service. By specifying username and password, an attacker connected to the router's web interface can execute arbitrary OS commands. The username and password fields are not sanitized correctly and are used as URL construction arguments, allowing URL redirection to an arbitrary server, downloading an arbitrary script file, and eventually executing the file in the device. This issue affects: Linksys MR8300 Router 1.0. |
| CVE-2022-26373 | Medium | 2022-08-18 | Not applicable | No public exploit | Non-transparent sharing of return predictor targets between contexts in some Intel(R) Processors may allow an authorized user to potentially enable information disclosure via local access. |
| CVE-2022-21233 | Medium | 2022-08-18 | Not applicable | No public exploit | Improper isolation of shared resources in some Intel(R) Processors may allow a privileged user to potentially enable information disclosure via local access. |
| CVE-2021-33060 | High | 2022-08-18 | Not applicable | No public exploit | Out-of-bounds write in the BIOS firmware for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access. |
| CVE-2022-36879 | Medium | 2022-07-27 | Not applicable | No public exploit | An issue was discovered in the Linux kernel through 5.18.14. xfrm_expand_policies in net/xfrm/xfrm_policy.c can cause a refcount to be dropped twice. |
| CVE-2022-29901 | Medium | 2022-07-12 | Not applicable | No public exploit | Intel microprocessor generations 6 to 8 are affected by a new Spectre variant that is able to bypass their retpoline mitigation in the kernel to leak arbitrary data. An attacker with unprivileged user access can hijack return instructions to achieve arbitrary speculative code execution under certain microarchitecture-dependent conditions. |
| CVE-2022-2068 | Critical | 2022-06-21 | Outside Waratek scope | Proof of concept only | In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze). |
| CVE-2022-21180 | Medium | 2022-06-15 | Not applicable | No public exploit | Improper input validation for some Intel(R) Processors may allow an authenticated user to potentially cause a denial of service via local access. |
| CVE-2022-30594 | High | 2022-05-12 | Not applicable | No public exploit | The Linux kernel before 5.17.2 mishandles seccomp permissions. The PTRACE_SEIZE code path allows attackers to bypass intended restrictions on setting the PT_SUSPEND_SECCOMP flag. |
| CVE-2022-21151 | Medium | 2022-05-12 | Not applicable | No public exploit | Processor optimization removal or modification of security-critical code for some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access. |
| CVE-2022-0005 | Low | 2022-05-12 | Not applicable | No public exploit | Sensitive information accessible by physical probing of JTAG interface for some Intel(R) Processors with SGX may allow an unprivileged user to potentially enable information disclosure via physical access. |
| CVE-2022-0004 | Medium | 2022-05-12 | Not applicable | No public exploit | Hardware debug modes and processor INIT setting that allow override of locks for some Intel(R) Processors in Intel(R) Boot Guard and Intel(R) TXT may allow an unauthenticated user to potentially enable escalation of privilege via physical access. |
| CVE-2021-33124 | Medium | 2022-05-12 | Not applicable | No public exploit | Out-of-bounds write in the BIOS authenticated code module for some Intel(R) Processors may allow a privileged user to potentially enable aescalation of privilege via local access. |
| CVE-2021-33123 | High | 2022-05-12 | Not applicable | No public exploit | Improper access control in the BIOS authenticated code module for some Intel(R) Processors may allow a privileged user to potentially enable aescalation of privilege via local access. |
| CVE-2022-1473 | High | 2022-05-03 | Not applicable | No public exploit | The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the memory occuppied by the removed hash table entries. This function is used when decoding certificates or keys. If a long lived process periodically decodes certificates or keys its memory usage will expand without bounds and the process might be terminated by the operating system causing a denial of service. Also traversing the empty hash table entries will take increasingly more time. Typically such long lived processes might be TLS clients or TLS servers configured to accept client certificate authentication. The function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). |
| CVE-2022-1434 | Medium | 2022-05-03 | Not applicable | No public exploit | The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key. This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at that point. Many application protocols require data to be sent from the client to the server first. Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0 client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both directions. In this case both clients and servers could be affected, regardless of the application protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0 endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is 1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). |
| CVE-2022-1343 | Medium | 2022-05-03 | Not applicable | No public exploit | The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful verification) even in the case where the response signing certificate fails to verify. It is anticipated that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the `OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a certificate verification failure. The normal expected return value in this case would be 0. This issue also impacts the command line OpenSSL "ocsp" application. When verifying an ocsp response with the "-no_cert_checks" option the command line application will report that the verification is successful even though it has in fact failed. In this case the incorrect successful response will also be accompanied by error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). |
| CVE-2022-1292 | Critical | 2022-05-03 | Outside Waratek scope | Proof of concept only | The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). |
| CVE-2022-0742 | Critical | 2022-03-18 | Not applicable | No public exploit | Memory leak in icmp6 implementation in Linux Kernel 5.13+ allows a remote attacker to DoS a host by making it go out-of-memory via icmp6 packets of type 130 or 131. We recommend upgrading past commit 2d3916f3189172d5c69d33065c3c21119fe539fc. |
| CVE-2021-33107 | Medium | 2022-02-09 | Not applicable | No public exploit | Insufficiently protected credentials in USB provisioning for Intel(R) AMT SDK before version 16.0.3, Intel(R) SCS before version 12.2 and Intel(R) MEBx before versions 11.0.0.0012, 12.0.0.0011, 14.0.0.0004 and 15.0.0.0004 may allow an unauthenticated user to potentially enable information disclosure via physical access. |
| CVE-2021-0156 | High | 2022-02-09 | Not applicable | No public exploit | Improper input validation in the firmware for some Intel(R) Processors may allow an authenticated user to potentially enable an escalation of privilege via local access. |