CVE-2025-29910

{"id": "CVE-2025-29910", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.5, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "PROOF_OF_CONCEPT", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "LOW", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-03-17T22:15:14.810", "references": [{"url": "https://github.com/nasa/CryptoLib/security/advisories/GHSA-p38w-p2r8-g6g5", "source": "security-advisories@github.com"}, {"url": "https://github.com/nasa/CryptoLib/security/advisories/GHSA-p38w-p2r8-g6g5", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Received", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-401"}]}], "descriptions": [{"lang": "en", "value": "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 memory leak vulnerability was identified in the `crypto_handle_incrementing_nontransmitted_counter` function of CryptoLib versions 1.3.3 and prior. This vulnerability can lead to resource exhaustion and degraded system performance over time, particularly in long-running processes or systems processing large volumes of data. The vulnerability is present in the `crypto_handle_incrementing_nontransmitted_counter` function within `crypto_tc.c`. The function allocates memory using `malloc` without ensuring the allocated memory is always freed. This issue can lead to resource exhaustion, reduced system performance, and potentially a Denial of Service (DoS) in environments where CryptoLib is used in long-running processes or with large volumes of data. Any system using CryptoLib, especially those handling high-throughput or continuous data streams, could be impacted. As of time of publication, no known patched versions are available."}, {"lang": "es", "value": "CryptoLib ofrece una soluci\u00f3n exclusivamente de software que utiliza el Protocolo de Seguridad de Enlace de Datos Espaciales CCSDS - Procedimientos Extendidos (SDLS-EP) para proteger las comunicaciones entre una nave espacial que ejecuta el Sistema de Vuelo (cFS) y una estaci\u00f3n terrestre. Se identific\u00f3 una vulnerabilidad de fuga de memoria en la funci\u00f3n `crypto_handle_incrementing_nontransmitted_counter` de las versiones 1.3.3 y anteriores de CryptoLib. Esta vulnerabilidad puede provocar el agotamiento de recursos y la degradaci\u00f3n del rendimiento del sistema con el tiempo, especialmente en procesos de larga duraci\u00f3n o sistemas que procesan grandes vol\u00famenes de datos. La vulnerabilidad est\u00e1 presente en la funci\u00f3n `crypto_handle_incrementing_nontransmitted_counter` dentro de `crypto_tc.c`. Esta funci\u00f3n asigna memoria mediante `malloc` sin garantizar que la memoria asignada siempre est\u00e9 libre. Este problema puede provocar el agotamiento de recursos, la reducci\u00f3n del rendimiento del sistema y, potencialmente, una denegaci\u00f3n de servicio (DoS) en entornos donde CryptoLib se utiliza en procesos de larga duraci\u00f3n o con grandes vol\u00famenes de datos. Cualquier sistema que utilice CryptoLib, especialmente aquellos que gestionan flujos de datos continuos o de alto rendimiento, podr\u00eda verse afectado. Al momento de la publicaci\u00f3n, no se conoc\u00edan versiones parcheadas."}], "lastModified": "2025-03-18T14:15:43.913", "sourceIdentifier": "security-advisories@github.com"}