Vuldb Updates

A vulnerability, which was classified as problematic, was found in Apple watchOS up to 9.3.1. This affects an unknown part of the component Foundation. Executing manipulation can lead to integer overflow. This vulnerability is registered as CVE-2023-27937. The attack needs to be launched locally. No exploit is available. You should upgrade the affected component.

A vulnerability was found in Apple macOS up to 13.2.1. It has been rated as problematic. This affects an unknown part of the component Foundation. This manipulation causes integer overflow. This vulnerability appears as CVE-2023-27937. The attack requires local access. There is no available exploit. Upgrading the affected component is advised.

A vulnerability was found in Apple iOS and iPadOS up to 16.3.1. It has been classified as problematic. The impacted element is an unknown function of the component Foundation. This manipulation causes integer overflow. This vulnerability is handled as CVE-2023-27937. It is possible to launch the attack on the local host. There is not any exploit available. Upgrading the affected component is recommended.

A vulnerability categorized as critical has been discovered in Apple macOS up to 13.2.1. Affected by this vulnerability is an unknown functionality of the component CommCenter. The manipulation results in out-of-bounds write. This vulnerability is known as CVE-2023-27936. Attacking locally is a requirement. No exploit is available. It is advisable to upgrade the affected component.

A vulnerability was found in Apple iOS and iPadOS up to 15.7.3 and classified as critical. Affected is an unknown function. Such manipulation leads to out-of-bounds write. This vulnerability is referenced as CVE-2023-27936. The attack can only be performed from a local environment. No exploit is available. It is suggested to upgrade the affected component.

A vulnerability classified as critical was found in Apple macOS up to 13.2.1. The affected element is an unknown function of the component dcerpc. The manipulation results in memory corruption. This vulnerability is identified as CVE-2023-27935. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.

A vulnerability identified as critical has been detected in Linux Kernel up to 6.4.15/6.5.2. The affected element is the function create_qp. This manipulation causes privilege escalation. The identification of this vulnerability is CVE-2023-53528. The attack needs to be done within the local network. There is no exploit available. You should upgrade the affected component.

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 5.15.131/6.1.53/6.5.3. This affects the function b_transaction. Performing manipulation results in buffer overflow. This vulnerability is known as CVE-2023-53526. Access to the local network is required for this attack. No exploit is available. It is advisable to upgrade the affected component.

A vulnerability categorized as critical has been discovered in Linux Kernel up to 6.0.18/6.1.4. Affected by this issue is the function qed_mcp_trace_dump of the file arch/x86/kernel/irq.c. Such manipulation leads to reachable assertion. This vulnerability is listed as CVE-2023-53509. The attack must be carried out from within the local network. There is no available exploit. It is advisable to upgrade the affected component.

A vulnerability classified as critical has been found in Linux Kernel up to 6.4.9. The impacted element is the function devlink_free. Performing manipulation results in denial of service. This vulnerability is cataloged as CVE-2023-53507. The attack must originate from the local network. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.1.42/6.4.7. Affected is the function ublk_ctrl_start_dev of the component ublk. The manipulation results in denial of service. This vulnerability is reported as CVE-2023-53508. The attacker must have access to the local network to execute the attack. No exploit exists. You should upgrade the affected component.

A vulnerability labeled as critical has been found in Linux Kernel up to 6.4.3. This issue affects some unknown processing of the component clk. The manipulation results in memory leak. This vulnerability is identified as CVE-2023-53505. The attack can only be performed from the local network. There is not any exploit available. The affected component should be upgraded.

A vulnerability labeled as critical has been found in Advantech WebAccess and VPN up to 1.1.4. The impacted element is the function AjaxDeviceController.ajaxDeviceAction of the component Search Parameter Handler. The manipulation results in sql injection. This vulnerability is cataloged as CVE-2025-34241. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded.

A vulnerability was found in Moby and classified as problematic. The affected element is an unknown function. Executing manipulation can lead to not failing securely. This vulnerability is handled as CVE-2023-28841. The attack can be executed remotely. There is not any exploit available. It is suggested to upgrade the affected component.

A vulnerability has been found in Moby 1.11/17.06.0/20.10.9/20.10.14/20.10.18 and classified as problematic. Impacted is an unknown function. Performing manipulation results in not failing securely. This vulnerability is known as CVE-2023-28840. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.

A vulnerability was found in runc up to 1.1.4. It has been declared as critical. The affected element is an unknown function of the file /proc of the component AppArmor. The manipulation results in preservation of permissions. This vulnerability was named CVE-2023-28642. The attack needs to be approached locally. There is no available exploit. It is recommended to upgrade the affected component.

A vulnerability was found in runc up to 1.1.4. It has been classified as critical. This impacts an unknown function of the file libcontainer/rootfs_linux.go of the component volume-mount Configuration. Performing manipulation results in improper access controls. This vulnerability is reported as CVE-2023-27561. The attacker must have access to the local network to execute the attack. No exploit exists.

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.12.28/6.14.6. Affected is the function erofs_onlinefolio_split of the component fileio. This manipulation causes allocation of resources. This vulnerability is tracked as CVE-2025-37999. The attack is only possible within the local network. No exploit exists. It is advisable to upgrade the affected component.

A vulnerability classified as critical has been found in dnsmasq up to 2.73rc6. Affected is the function parse_hex of the file src/util.c of the component Config File Handler. The manipulation of the argument i leads to heap-based buffer overflow. This vulnerability is uniquely identified as CVE-2025-12198. Local access is required to approach this attack. Moreover, an exploit is present. The real existence of this vulnerability is still doubted at the moment. Based on the analysis by MITRE and review of community feedback, the reported conditions represent expected and intentional behavior within dnsmasq's documented design, rather than security vulnerabilities. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability classified as problematic was found in dnsmasq up to 2.73rc6. Affected by this vulnerability is the function check_servers of the file src/network.c of the component Config File Handler. The manipulation results in null pointer dereference. This vulnerability was named CVE-2025-12199. The attack needs to be approached locally. In addition, an exploit is available. It is still unclear if this vulnerability genuinely exists. Based on the analysis by MITRE and review of community feedback, the reported conditions represent expected and intentional behavior within dnsmasq's documented design, rather than security vulnerabilities. The vendor was contacted early about this disclosure but did not respond in any way.