CVE-2025-27508

{"id": "CVE-2025-27508", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2025-03-05T22:15:35.867", "references": [{"url": "https://github.com/NationalSecurityAgency/emissary/commit/da3a81a8977577597ff2a944820a5ae4e9762368", "source": "security-advisories@github.com"}, {"url": "https://github.com/NationalSecurityAgency/emissary/security/advisories/GHSA-hw43-fcmm-3m5g", "source": "security-advisories@github.com"}, {"url": "https://github.com/NationalSecurityAgency/emissary/security/advisories/GHSA-hw43-fcmm-3m5g", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-327"}]}], "descriptions": [{"lang": "en", "value": "Emissary is a P2P based data-driven workflow engine. The ChecksumCalculator class within allows for hashing and checksum generation, but it includes or defaults to algorithms that are no longer recommended for secure cryptographic use cases (e.g., SHA-1, CRC32, and SSDEEP). These algorithms, while possibly valid for certain non-security-critical tasks, can expose users to security risks if used in scenarios where strong cryptographic guarantees are required. This issue is fixed in 8.24.0."}, {"lang": "es", "value": "Emissary es un motor de flujo de trabajo basado en datos P2P. La clase ChecksumCalculator permite la generaci\u00f3n de sumas de comprobaci\u00f3n y hash, pero incluye o utiliza de forma predeterminada algoritmos que ya no se recomiendan para casos de uso criptogr\u00e1fico seguro (por ejemplo, SHA-1, CRC32 y SSDEEP). Estos algoritmos, si bien pueden ser v\u00e1lidos para ciertas tareas no cr\u00edticas para la seguridad, pueden exponer a los usuarios a riesgos de seguridad si se utilizan en escenarios en los que se requieren garant\u00edas criptogr\u00e1ficas s\u00f3lidas. Este problema se solucion\u00f3 en 8.24.0."}], "lastModified": "2025-03-07T18:15:48.033", "sourceIdentifier": "security-advisories@github.com"}