Natalie Silvanovich

The issue is related to an out-of-bounds write in memory initialization in libsavsvc.so. This allows local attackers to write out-of-bounds memory. The problem is present prior to the SMR May-2025 Release 1.

The issue is related to an out-of-bounds write in parsing media files. This allows local attackers to write out-of-bounds memory. The problem is associated with the libsavsvc.so component prior to the SMR May-2025 Release 1.

The issue allows physical attackers to temporarily access the recent app list through an authentication bypass using an alternate path in Dex Mode. This is possible prior to the SMR Dec-2024 Release 1.

The issue allows physical attackers to copy apk files to an arbitrary path with ThemeCenter privilege. This is due to a path traversal vulnerability in ThemeCenter.

The issue is an out-of-bounds write in libswmfextractor.so, allowing local attackers to execute arbitrary code. This enables attackers to potentially gain control over the system. No information is provided about the estimated number of potentially affected devices worldwide or real-world incidents where this issue was exploited.

The vulnerable software is Samsung's Monkey's Audio (APE) decoder, used in Samsung smartphones running Android versions 12, 13, and 14. The vulnerability is a high-severity out-of-bounds write flaw that allows remote attackers to execute arbitrary code on the device without any user interaction. This is a zero-click vulnerability, meaning that attackers can exploit it without the user having to click on anything. The vulnerability is exploited through a specially crafted audio file sent via Google Messages on RCS-enabled devices, such as the Galaxy S23 and S24. A proof-of-concept (PoC) for the vulnerability has been released, and Samsung has issued a security update to patch the flaw. Users are advised to update their devices to the latest software version, SMR Dec-2024 Release 1, to fix the vulnerability. It is estimated that millions of devices are at risk due to this vulnerability. The vulnerable versions are prior to SMR Dec-2024 Release 1. #Samsung #Android #MonkeyAudio #GoogleProjectZero #Cybersecurity #ZeroClickVulnerability #RCS #GalaxyS23 #GalaxyS24

The issue is related to a use after free in WebRTC, allowing a remote attacker to potentially exploit heap corruption via a crafted WebRTC session. This could lead to arbitrary code execution or denial of service.

A memory corruption issue was addressed with improved state management. This issue may allow an app to cause a denial-of-service.

The issue allows an app to potentially execute arbitrary code with kernel privileges due to insufficient checks.

A buffer overflow issue was addressed with improved bounds checking, which may allow a remote user to cause kernel code execution.

The issue is related to the exposure of the state of process memory, potentially allowing an attacker to gain insight into arbitrary areas of the product's memory. This could be used to potentially expose protected information.

A buffer overflow vulnerability was discovered in Zoom software, potentially allowing a malicious actor to crash the service or application, or leverage this vulnerability to execute arbitrary code. The issue is related to a buffer overflow in memory, which can be exploited by a remote attacker. This vulnerability can lead to the execution of arbitrary code, potentially allowing an attacker to gain control over the affected system.

The issue is related to a buffer overflow that could occur when parsing and validating SCTP chunks in WebRTC, potentially leading to memory corruption and a crash. This could allow a remote attacker to access confidential data, compromise its integrity, and cause a denial of service.

The issue is related to out-of-bounds reads in the `sctp load addresses from init` function of the usrsctp implementation. This can potentially allow a remote attacker to cause a denial of service.

The issue is related to an out of bounds write in the WebRTC component of Google Chrome, which can be exploited by a remote attacker. This exploitation can lead to access to confidential data, disruption of data integrity, and potentially cause a denial of service. The attacker can exploit heap corruption via a crafted video stream.

The issue is related to an out of bounds write in the WebRTC component of Google Chrome, which can be exploited by a remote attacker. This exploitation can lead to access to confidential data, disruption of data integrity, and potentially cause a denial of service via a crafted video stream.

A use after free issue was addressed with improved memory management. A remote attacker may be able to cause arbitrary code execution.

A memory corruption issue was addressed with improved input validation. A remote attacker may be able to cause unexpected application termination or arbitrary code execution.

The issue allows an attacker to trigger a use-after-free in an application deserializing an untrusted NSDictionary. This can be exploited by an attacker.

The issue is related to an out-of-bounds read that has been addressed with improved input validation. A remote attacker may be able to leak memory.