Use after free in Aura in Google Chrome prior to 139.0.7258.127 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
Search vulnerabilities
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: WCNCR00441507; Issue ID: MSV-4112.
ABCD ABCD2 buscar_integrada.php cross site scripting
A vulnerability was determined in ABCD ABCD2 up to 2.2.0-beta-1. Impacted is an unknown function of the file /buscar_integrada.php. Executing a manipulation of the argument Sub_Expresion can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. The developer explains, that "this script has been completely redesigned after this version".
Meshtastic firmware allows forged DMs with no PKC to show up as encrypted
Meshtastic is an open source mesh networking solution. The Meshtastic firmware (starting from version 2.5) introduces asymmetric encryption (PKI) for direct messages, but when the `pki_encrypted` flag is missing, the firmware silently falls back to legacy AES-256-CTR channel encryption. This was an intentional decision to maintain backwards compatibility. However, the end-user applications, like Web app, iOS/Android app, and applications built on top of Meshtastic using the SDK, did not have a way to differentiate between end-to-end encrypted DMs and the legacy DMs. This creates a downgrade attack path where adversaries who know a shared channel key can craft and inject spoofed direct messages that are displayed as if they were PKC encrypted. Users are not given any feedback of whether a direct message was decrypted with PKI or with legacy symmetric encryption, undermining the expected security guarantees of the PKI rollout. Version 2.7.15 fixes this issue.
In KeyInstall, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS09475476; Issue ID: MSV-2599.
In wlan AP FW, there is a possible out of bounds write due to improper input validation. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00389074; Issue ID: MSV-1803.
In da, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS09291294; Issue ID: MSV-2061.
Use After Free in DSP Service
Memory corruption while handling multuple IOCTL calls from userspace for remote invocation.
Improper Validation of Array Index in Camera
Memory corruption may occur during the synchronization of the camera`s frame processing pipeline.
Permissions, Privileges, and Access Controls in Video Analytics and Processing
Information disclosure may occur due to improper permission and access controls to Video Analytics engine.
Improper Input Validation in Automotive OS Platform
Memory corruption may occur due to improper input validation in clock device.
Improper Validation of Array Index in Audio
Memory corruption may occur while validating ports and channels in Audio driver.
Improper Input Validation in Automotive OS Platform
Memory corruption may occur during communication between primary and guest VM.
Use After Free in Automotive Android OS
Memory corruption may occur while accessing a variable during extended back to back tests.
NULL Pointer Dereference in Display
Memory corruption in display driver while detaching a device.
Time-of-check Time-of-use (TOCTOU) Race Condition in Automotive Vehicle Networks
Memory corruption may occur while processing message from frontend during allocation.
Improper Input Validation in Automotive OS Platform
Memory corruption while reading a value from a buffer controlled by the Guest Virtual Machine.
Improper Input Validation in Automotive OS Platform
Memory corruption while processing input message passed from FE driver.
Improper Input Validation in Automotive OS Platform
Memory corruption while reading a type value from a buffer controlled by the Guest Virtual Machine.
Time-of-check Time-of-use (TOCTOU) Race Condition in Automotive OS Platform
Memory corruption may occur in keyboard virtual device due to guest VM interaction.