Show filters
410 Total Results
Displaying 171-180 of 410
Sort by:
Attacker Value
Unknown
CVE-2024-1062
Disclosure Date: February 12, 2024 (last updated February 18, 2025)
A heap overflow flaw was found in 389-ds-base. This issue leads to a denial of service when writing a value larger than 256 chars in log_entry_attr.
0
Attacker Value
Unknown
CVE-2023-52429
Disclosure Date: February 12, 2024 (last updated February 27, 2024)
dm_table_create in drivers/md/dm-table.c in the Linux kernel through 6.7.4 can attempt to (in alloc_targets) allocate more than INT_MAX bytes, and crash, because of a missing check for struct dm_ioctl.target_count.
0
Attacker Value
Unknown
CVE-2024-1151
Disclosure Date: February 11, 2024 (last updated November 12, 2024)
A vulnerability was reported in the Open vSwitch sub-component in the Linux Kernel. The flaw occurs when a recursive operation of code push recursively calls into the code block. The OVS module does not validate the stack depth, pushing too many frames and causing a stack overflow. As a result, this can lead to a crash or other related issues.
0
Attacker Value
Unknown
CVE-2024-0229
Disclosure Date: February 09, 2024 (last updated October 19, 2024)
An out-of-bounds memory access flaw was found in the X.Org server. This issue can be triggered when a device frozen by a sync grab is reattached to a different master device. This issue may lead to an application crash, local privilege escalation (if the server runs with extended privileges), or remote code execution in SSH X11 forwarding environments.
0
Attacker Value
Unknown
CVE-2024-1312
Disclosure Date: February 08, 2024 (last updated February 15, 2024)
A use-after-free flaw was found in the Linux kernel's Memory Management subsystem when a user wins two races at the same time with a fail in the mas_prev_slot function. This issue could allow a local user to crash the system.
0
Attacker Value
Unknown
CVE-2024-20290
Disclosure Date: February 07, 2024 (last updated February 16, 2024)
A vulnerability in the OLE2 file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.
This vulnerability is due to an incorrect check for end-of-string values during scanning, which may result in a heap buffer over-read. An attacker could exploit this vulnerability by submitting a crafted file containing OLE2 content to be scanned by ClamAV on an affected device. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software and consuming available system resources.
For a description of this vulnerability, see the ClamAV blog .
0
Attacker Value
Unknown
CVE-2024-1284
Disclosure Date: February 07, 2024 (last updated February 15, 2024)
Use after free in Mojo in Google Chrome prior to 121.0.6167.160 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
0
Attacker Value
Unknown
CVE-2024-0690
Disclosure Date: February 06, 2024 (last updated May 22, 2024)
An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG configuration in some scenarios. Information is still included in the output in certain tasks, such as loop items. Depending on the task, this issue may include sensitive information, such as decrypted secret values.
0
Attacker Value
Unknown
CVE-2024-22667
Disclosure Date: February 05, 2024 (last updated February 06, 2025)
Vim before 9.0.2142 has a stack-based buffer overflow because did_set_langmap in map.c calls sprintf to write to the error buffer that is passed down to the option callback functions.
0
Attacker Value
Unknown
CVE-2023-6780
Disclosure Date: January 31, 2024 (last updated February 13, 2024)
An integer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when these functions are called with a very long message, leading to an incorrect calculation of the buffer size to store the message, resulting in undefined behavior. This issue affects glibc 2.37 and newer.
0