3376 matches found
EUVD-2025-203385
A security issue exists due to improper handling of malformed CIP packets during fuzzing. The controller enters a hard fault with solid red Fault LED and becomes unresponsive. Upon power cycle, the controller will enter recoverable fault where the MS LED and Fault LED become flashing red and...
CVE-2025-13823
A security issue was found in the IPv6 stack in the Micro850 and Micro870 controllers when the controllers received multiple malformed packets during fuzzing. The controllers will go into recoverable fault with fault code 0xFE60. To recover the controller, clear the fault...
CVE-2025-13824
A security issue exists due to improper handling of malformed CIP packets during fuzzing. The controller enters a hard fault with solid red Fault LED and becomes unresponsive. Upon power cycle, the controller will enter recoverable fault where the MS LED and Fault LED become flashing red and...
CVE-2025-13824 Micro820®, Micro850®, Micro870® – Specialized Fuzzing Vulnerabilities
A security issue exists due to improper handling of malformed CIP packets during fuzzing. The controller enters a hard fault with solid red Fault LED and becomes unresponsive. Upon power cycle, the controller will enter recoverable fault where the MS LED and Fault LED become flashing red and...
CVE-2025-13824
CVE-2025-13824 affects Rockwell Automation Micro820, Micro850, and Micro870 controllers. The vulnerability stems from improper handling of malformed CIP packets in the IPv6 stack during fuzzing, causing the controller to enter a hard fault and become unresponsive. On power cycle, it enters a reco...
CVE-2025-13823
CVE-2025-13823 affects Rockwell Automation Micro850 and Micro870 controllers in their IPv6 stack. When receiving multiple malformed packets during fuzzing, the controllers enter a recoverable fault with fault code 0xFE60. To recover, the fault must be cleared. Several connected advisories corrobo...
CVE-2025-13823 Micro820®, Micro850®, Micro870® – Specialized Fuzzing Vulnerabilities
A security issue was found in the IPv6 stack in the Micro850 and Micro870 controllers when the controllers received multiple malformed packets during fuzzing. The controllers will go into recoverable fault with fault code 0xFE60. To recover the controller, clear the fault...
CVE-2025-13823 Micro820®, Micro850®, Micro870® – Specialized Fuzzing Vulnerabilities
A security issue was found in the IPv6 stack in the Micro850 and Micro870 controllers when the controllers received multiple malformed packets during fuzzing. The controllers will go into recoverable fault with fault code 0xFE60. To recover the controller, clear the fault...
PT-2025-51237
Name of the Vulnerable Software and Affected Versions Versions affected versions not specified Description A security issue arises from improper handling of malformed CIP packets during fuzzing. This causes the controller to enter a hard fault, indicated by a solid red Fault LED and...
PT-2025-51236
Name of the Vulnerable Software and Affected Versions Micro850 and Micro870 controllers affected versions not specified Description An issue exists in the IPv6 stack of the Micro850 and Micro870 controllers. The controllers may enter a recoverable fault state fault code 0xFE60 when receiving...
CVE-2025-13823: Dependency on Vulnerable Third-Party Component
A security issue was found in the IPv6 stack in the Micro850 and Micro870 controllers when the controllers received multiple malformed packets during fuzzing. The controllers will go into recoverable fault with fault code 0xFE60. To recover the controller, clear the fault...
bitcoin-core:crypto_hkdf_hmac_sha256_l32: Use-of-uninitialized-value in LLVMFuzzerInitialize
Detailed Report: https://oss-fuzz.com/testcase?key=6498736437264384 Project: bitcoin-core Fuzzing Engine: libFuzzer Fuzz Target: cryptohkdfhmacsha256l32 Job Type: libfuzzermsanbitcoin-core Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: LLVMFuzzerInitialize...
SqlScanner
SqlScanner SQL Injection Scanner deve...
EUVD-2022-55717
In the Linux kernel, the following vulnerability has been resolved: io-wq: Fix memory leak in worker creation If the CPU mask allocation for a node fails, then the memory allocated for the 'iowqe' struct of the current node doesn't get freed on the error handling path, since it has not yet been...
CVE-2022-50639
In the Linux kernel, the following vulnerability has been resolved: io-wq: Fix memory leak in worker creation If the CPU mask allocation for a node fails, then the memory allocated for the 'iowqe' struct of the current node doesn't get freed on the error handling path, since it has not yet been...
DEBIAN-CVE-2022-50639
In the Linux kernel, the following vulnerability has been resolved: io-wq: Fix memory leak in worker creation If the CPU mask allocation for a node fails, then the memory allocated for the 'iowqe' struct of the current node doesn't get freed on the error handling path, since it has not yet been...
CVE-2022-50639
CVE-2022-50639 describes a Linux kernel issue where, during io-wq worker creation, a CPU mask allocation failure could leak memory from the io_wqe structure if not yet added to the wqes array. The available connected sources (Astra Linux, EUVD, OSV, NVD/NIST, etc.) report that this vulnerability ...
CVE-2022-50639
In the Linux kernel, the following vulnerability has been resolved: io-wq: Fix memory leak in worker creation If the CPU mask allocation for a node fails, then the memory allocated for the 'iowqe' struct of the current node doesn't get freed on the error handling path, since it has not yet been...
CVE-2023-53761
In the Linux kernel, the following vulnerability has been resolved: USB: usbtmc: Fix direction for 0-length ioctl control messages The syzbot fuzzer found a problem in the usbtmc driver: When a user submits an ioctl for a 0-length control transfer, the driver does not check that the direction is...