CVE-2004-0607: The eay_check_x509cert function in KAME Racoon successfully verifies certificates even when OpenSSL validat...

Security readout for executives and security teams

This flaw means KAME Racoon could accept a certificate as valid even after OpenSSL rejected it. In business terms, an attacker might bypass certificate-based authentication on affected deployments. The source bundle does not provide CVSS, confirmed affected versions, or evidence of active exploitation. Exposure is most likely where legacy KAME Racoon is deployed and relies on certificate validation for remote authentication. The supplied affected-product data is marked n/a, so teams must confirm exposure through package inventories, system baselines, and vendor advisories. Prioritize if Racoon remains in production, especially on remote access or gateway systems. For modern environments without KAME Racoon, the main task is confirming absence rather than launching an emergency response. Mitigation focus: Check vendor guidance from Red Hat, Gentoo, SCO, and upstream release notes.; Update or replace affected KAME Racoon packages using supported vendor channels.; Identify systems still running Racoon or legacy KAME-derived packages..

Prepared

Jun 30, 2026, 05:41 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.