Total
285589 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2025-29912 | 2025-03-17 | N/A | ||
| CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) and a ground station. In versions 1.3.3 and prior, an unsigned integer underflow in the `Crypto_TC_ProcessSecurity` function of CryptoLib leads to a heap buffer overflow. The vulnerability is triggered when the `fl` (frame length) field in a Telecommand (TC) packet is set to 0. This underflow causes the frame length to be interpreted as 65535, resulting in out-of-bounds memory access. This critical vulnerability can be exploited to cause a denial of service (DoS) or potentially achieve remote code execution. Users of CryptoLib are advised to apply the recommended patch or avoid processing untrusted TC packets until a fix is available. | ||||
| CVE-2025-29911 | 2025-03-17 | N/A | ||
| CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) and a ground station. A critical heap buffer overflow vulnerability was identified in the `Crypto_AOS_ProcessSecurity` function of CryptoLib versions 1.3.3 and prior. This vulnerability allows an attacker to trigger a Denial of Service (DoS) or potentially execute arbitrary code (RCE) by providing a maliciously crafted AOS frame with an insufficient length. The vulnerability lies in the function `Crypto_AOS_ProcessSecurity`, specifically during the processing of the Frame Error Control Field (FECF). The affected code attempts to read from the `p_ingest` buffer at indices `current_managed_parameters_struct.max_frame_size - 2` and `current_managed_parameters_struct.max_frame_size - 1` without verifying if `len_ingest` is sufficiently large. This leads to a heap buffer overflow when `len_ingest` is smaller than `max_frame_size`. As of time of publication, no known patched versions exist. | ||||
| CVE-2025-27768 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2025-27767 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2025-27766 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2025-27765 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2025-27764 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2025-27763 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2025-27762 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2025-27761 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2025-27760 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2024-56506 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2024-56505 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2024-56504 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2024-56503 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2024-56502 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2024-56501 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2024-56500 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2024-56499 | 2025-03-17 | N/A | ||
| Not used | ||||
| CVE-2024-56498 | 2025-03-17 | N/A | ||
| Not used | ||||