Vulnerabilities

Integer Overflow or Wraparound vulnerability in yoyofr modizer.This issue affects modizer: before 4.1.1.

Mitigation bypass in the Privacy: Anti-Tracking component. This vulnerability affects Firefox

Out-of-bounds Write vulnerability in ixray-team ixray-1.6-stcop.This issue affects ixray-1.6-stcop: before 1.3.

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in ixray-team ixray-1.6-stcop.This issue affects ixray-1.6-stcop: before 1.3.

Improper Control of Generation of Code ('Code Injection') vulnerability in pilgrimage233 Minecraft-Rcon-Manage.This issue affects Minecraft-Rcon-Manage: before 3.0.

improper pointer arithmetic<br /> <br /> vulnerability in ProjectSkyfire SkyFire_548.This issue affects SkyFire_548: before 5.4.8-stable5.

Out-of-bounds Read vulnerability in Rinnegatamante lpp-vita.This issue affects lpp-vita: before lpp-vita r6.

Access of Resource Using Incompatible Type (&amp;#39;Type Confusion&amp;#39;) vulnerability in themrdemonized xray-monolith.This issue affects xray-monolith: before 2025.12.30.

Use-after-free in the Layout: Scrolling and Overflow component. This vulnerability affects Firefox

The vulnerability stems from an incorrect error-checking logic in the CreateCounter() function (in threadx/utility/rtos_compatibility_layers/OSEK/tx_osek.c) when handling the return value of osek_get_counter(). Specifically, the current code checks if cntr_id equals 0u to determine failure, but @osek_get_counter() actually returns E_OS_SYS_STACK (defined as 12U) when it fails. This mismatch causes the error branch to never execute even when the counter pool is exhausted.<br /> <br /> As a result, when the counter pool is depleted, the code proceeds to cast the error code (12U) to a pointer (OSEK_COUNTER *), creating a wild pointer. Subsequent writes to members of this pointer lead to writes to illegal memory addresses (e.g., 0x0000000C), which can trigger immediate HardFaults or silent memory corruption.<br /> <br /> This vulnerability poses significant risks, including potential denial-of-service attacks (via repeated calls to exhaust the counter pool) and unauthorized memory access.

Issue summary: An invalid or NULL pointer dereference can happen in<br /> an application processing a malformed PKCS#12 file.<br /> <br /> Impact summary: An application processing a malformed PKCS#12 file can be<br /> caused to dereference an invalid or NULL pointer on memory read, resulting<br /> in a Denial of Service.<br /> <br /> A type confusion vulnerability exists in PKCS#12 parsing code where<br /> an ASN1_TYPE union member is accessed without first validating the type,<br /> causing an invalid pointer read.<br /> <br /> The location is constrained to a 1-byte address space, meaning any<br /> attempted pointer manipulation can only target addresses between 0x00 and 0xFF.<br /> This range corresponds to the zero page, which is unmapped on most modern<br /> operating systems and will reliably result in a crash, leading only to a<br /> Denial of Service. Exploiting this issue also requires a user or application<br /> to process a maliciously crafted PKCS#12 file. It is uncommon to accept<br /> untrusted PKCS#12 files in applications as they are usually used to store<br /> private keys which are trusted by definition. For these reasons, the issue<br /> was assessed as Low severity.<br /> <br /> The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,<br /> as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.<br /> <br /> OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br /> <br /> OpenSSL 1.0.2 is not affected by this issue.

Loop with Unreachable Exit Condition (&amp;#39;Infinite Loop&amp;#39;) vulnerability in ixray-team ixray-1.6-stcop.This issue affects ixray-1.6-stcop: before 1.3.