Hcamael

An out-of-bounds read occurs when a program reads data outside the intended boundary of a buffer. Processing a maliciously crafted font may result in the disclosure of process memory.

An out-of-bounds write occurs due to insufficient input validation. This flaw allows an application to corrupt process memory or cause unexpected system termination.

An out-of-bounds write issue occurs due to insufficient bounds checking. Processing a maliciously crafted video file can lead to unexpected app termination. An out-of-bounds write is a condition where the program writes data past the end of the intended buffer, potentially corrupting memory.

Processing a maliciously crafted video file may lead to unexpected app termination or corrupt process memory due to improper memory handling.

An out-of-bounds read occurs due to insufficient input validation. This flaw allows an application to read kernel memory or cause unexpected system termination.

An out-of-bounds write issue exists where an application can write data past the end of a defined memory buffer. This can lead to unexpected system termination or the corruption of kernel memory, which is the core part of the operating system that manages hardware and system resources.

An out-of-bounds write issue exists where an application can write data past the end of a defined memory buffer. This can lead to kernel memory corruption or unexpected system termination.

An out-of-bounds write issue exists where an application may cause unexpected system termination or corrupt kernel memory. This occurs due to insufficient bounds checking, which is a process of verifying that a program does not access memory outside the boundaries of a predefined buffer.

Processing a maliciously crafted 3D model can lead to memory corruption due to an integer overflow, which occurs when an arithmetic operation attempts to create a numeric value that exceeds the maximum size of the integer type used to store it.

The software fails to honor the `disableFileAccess` and `disableUrlAccess` sandbox options when message content is resolved through the public plugin API `MailMessage.resolveContent()` using the legacy three-argument signature `resolveContent(data, key, callback)`. This occurs because `shared.resolveContent()` normalizes the missing `options` argument to an empty object, causing the `resolveContentValue()` function to skip access-control checks and reach `nmfetch(url)` or `fs.createReadStream(path)`. Consequently, application or plugin code resolving untrusted content (such as html, text, attachment `path`, or `href`) can be manipulated to read arbitrary local files or perform server-side request forgery (SSRF), which is when an attacker induces a server to make requests to an unintended location, bypassing the enabled sandbox.

A site isolation issue exists within the Graphics: WebRender component. Site isolation is a security mechanism that ensures web pages from different sites are processed in separate processes to prevent one site from accessing data from another.

Discord moderation actions lack proper authorization. This allows a lower-trust caller or a configured input path to execute moderation tasks that should require a stronger authorization or policy check. The actual impact is determined by the operator's configuration and whether lower-trust input can access the affected path.

The issue is related to an elevation-of-privilege vulnerability in the Windows Kernel, which can be caused by a buffer overflow. This vulnerability allows an attacker to potentially increase their privileges on the system. There is no information provided about the estimated number of potentially affected devices worldwide or real-world incidents where this issue was exploited.