Show filters
1,609 Total Results
Displaying 461-470 of 1,609
Sort by:
Attacker Value
Unknown
CVE-2023-3036
Disclosure Date: June 14, 2023 (last updated February 25, 2025)
An unchecked read in NTP server in github.com/cloudflare/cfnts prior to commit 783490b https://github.com/cloudflare/cfnts/commit/783490b913f05e508a492cd7b02e3c4ec2297b71 enabled a remote attacker to trigger a panic by sending an NTSAuthenticator packet with extension length longer than the packet contents.
0
Attacker Value
Unknown
CVE-2023-28601
Disclosure Date: June 13, 2023 (last updated February 25, 2025)
Zoom for Windows clients prior to 5.14.0 contain an improper restriction of operations within the bounds of a memory buffer vulnerability. A malicious user may alter protected Zoom Client memory buffer potentially causing integrity issues within the Zoom Client.
0
Attacker Value
Unknown
CVE-2023-33124
Disclosure Date: June 13, 2023 (last updated February 25, 2025)
A vulnerability has been identified in JT2Go (All versions < V14.2.0.3), Teamcenter Visualization V13.2 (All versions < V13.2.0.13), Teamcenter Visualization V13.3 (All versions < V13.3.0.10), Teamcenter Visualization V14.0 (All versions < V14.0.0.6), Teamcenter Visualization V14.1 (All versions < V14.1.0.8), Teamcenter Visualization V14.2 (All versions < V14.2.0.3). The affected applications contain a memory corruption vulnerability while parsing specially crafted CGM files. This could allow an attacker to execute code in the context of the current process.
0
Attacker Value
Unknown
CVE-2023-34341
Disclosure Date: June 12, 2023 (last updated February 25, 2025)
AMI BMC contains a vulnerability in the SPX REST API, where an
attacker with the required privileges can read and write to arbitrary locations
within the memory context of the IPMI server process, which may lead to code
execution, denial of service, information disclosure, or data tampering.
0
Attacker Value
Unknown
CVE-2023-21628
Disclosure Date: June 06, 2023 (last updated February 25, 2025)
Memory corruption in WLAN HAL while processing WMI-UTF command or FTM TLV1 command.
0
Attacker Value
Unknown
CVE-2022-40533
Disclosure Date: June 06, 2023 (last updated February 25, 2025)
Transient DOS due to untrusted Pointer Dereference in core while sending USB QMI request.
0
Attacker Value
Unknown
CVE-2022-33267
Disclosure Date: June 06, 2023 (last updated February 25, 2025)
Memory corruption in Linux while sending DRM request.
0
Attacker Value
Unknown
CVE-2023-27285
Disclosure Date: June 05, 2023 (last updated February 25, 2025)
IBM Aspera Connect 4.2.5 and IBM Aspera Cargo 4.2.5 is vulnerable to a buffer overflow, caused by improper bounds checking. An attacker could overflow a buffer and execute arbitrary code on the system. IBM X-Force ID: 248625.
0
Attacker Value
Unknown
CVE-2023-2977
Disclosure Date: June 01, 2023 (last updated February 25, 2025)
A vulnerbility was found in OpenSC. This security flaw cause a buffer overrun vulnerability in pkcs15 cardos_have_verifyrc_package. The attacker can supply a smart card package with malformed ASN1 context. The cardos_have_verifyrc_package function scans the ASN1 buffer for 2 tags, where remaining length is wrongly caculated due to moved starting pointer. This leads to possible heap-based buffer oob read. In cases where ASAN is enabled while compiling this causes a crash. Further info leak or more damage is possible.
0
Attacker Value
Unknown
CVE-2023-33975
Disclosure Date: May 30, 2023 (last updated February 25, 2025)
RIOT-OS, an operating system for Internet of Things (IoT) devices, contains a network stack with the ability to process 6LoWPAN frames. In version 2023.01 and prior, an attacker can send a crafted frame to the device resulting in an out of bounds write in the packet buffer. The overflow can be used to corrupt other packets and the allocator metadata. Corrupting a pointer will easily lead to denial of service. While carefully manipulating the allocator metadata gives an attacker the possibility to write data to arbitrary locations and thus execute arbitrary code. This issue is fixed in pull request 19680. As a workaround, disable support for fragmented IP datagrams.
0