{"dataType": "CVE_RECORD", "cveMetadata": {"state": "PUBLISHED", "cveId": "CVE-2025-30095", "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca", "assignerShortName": "mitre", "dateUpdated": "2025-04-11T13:12:06.783Z", "dateReserved": "2025-03-17T00:00:00.000Z", "datePublished": "2025-03-31T00:00:00.000Z"}, "containers": {"cna": {"affected": [{"defaultStatus": "unaffected", "product": "VyOS", "vendor": "VyOS", "versions": [{"lessThan": "1.4.2", "status": "affected", "version": "0", "versionType": "custom"}, {"lessThan": "1.5-stream-2025-Q2", "status": "affected", "version": "1.5", "versionType": "custom"}]}], "descriptions": [{"lang": "en", "value": "VyOS 1.3 through 1.5 (fixed in 1.4.2) or any Debian-based system using dropbear in combination with live-build has the same Dropbear private host keys across different installations. Thus, an attacker can conduct active man-in-the-middle attacks against SSH connections if Dropbear is enabled as the SSH daemon. I n VyOS, this is not the default configuration for the system SSH daemon, but is for the console service. To mitigate this, one can run \"rm -f /etc/dropbear/*key*\" and/or \"rm -f /etc/dropbear-initramfs/*key*\" and then dropbearkey -t rsa -s 4096 -f /etc/dropbear_rsa_host_key and reload the service or reboot the system before using Dropbear as the SSH daemon (this clears out all keys mistakenly built into the release image) or update to the latest version of VyOS 1.4 or 1.5. Note that this vulnerability is not unique to VyOS and may appear in any Debian-based Linux distribution that uses Dropbear in combination with live-build, which has a safeguard against this behavior in OpenSSH but no equivalent one for Dropbear."}], "problemTypes": [{"descriptions": [{"cweId": "CWE-321", "description": "CWE-321 Use of Hard-coded Cryptographic Key", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca", "shortName": "mitre", "dateUpdated": "2025-04-11T13:12:06.783Z"}, "references": [{"url": "https://github.com/vyos/"}, {"url": "https://vyos.net/get/stream/#1.5-2025-Q1"}, {"url": "https://blog.vyos.io/vyos-stream-1.5-2025-q1"}, {"url": "https://vyos.dev/T7217"}, {"url": "https://blog.vyos.io/vyos-project-march-2025-update"}], "x_generator": {"engine": "enrichogram 0.0.1"}, "metrics": [{"cvssV3_1": {"version": "3.1", "baseScore": 9, "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H"}}]}}, "dataVersion": "5.1"}

{}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "VyOS 1.3 through 1.5 (fixed in 1.4.2) or any Debian-based system using dropbear in combination with live-build has the same Dropbear private host keys across different installations. Thus, an attacker can conduct active man-in-the-middle attacks against SSH connections if Dropbear is enabled as the SSH daemon. I n VyOS, this is not the default configuration for the system SSH daemon, but is for the console service. To mitigate this, one can run \"rm -f /etc/dropbear/*key*\" and/or \"rm -f /etc/dropbear-initramfs/*key*\" and then dropbearkey -t rsa -s 4096 -f /etc/dropbear_rsa_host_key and reload the service or reboot the system before using Dropbear as the SSH daemon (this clears out all keys mistakenly built into the release image) or update to the latest version of VyOS 1.4 or 1.5. Note that this vulnerability is not unique to VyOS and may appear in any Debian-based Linux distribution that uses Dropbear in combination with live-build, which has a safeguard against this behavior in OpenSSH but no equivalent one for Dropbear."}, {"lang": "es", "value": "VyOS 1.3 a 1.5 (corregida en 1.4.2) o cualquier sistema basado en Debian que utilice dropbear en combinaci\u00f3n con live-build tiene las mismas claves de host privadas de Dropbear en diferentes instalaciones. Por lo tanto, un atacante puede realizar ataques de intermediario activos contra conexiones SSH si Dropbear est\u00e1 habilitado como daemon SSH. En VyOS, esta no es la configuraci\u00f3n predeterminada para el daemon SSH del sistema, sino para el servicio de consola. Para mitigar esto, se puede ejecutar \"rm -f /etc/dropbear/*key*\" o \"rm -f /etc/dropbear-initramfs/*key*\" y luego \"dropbearkey -t rsa -s 4096 -f /etc/dropbear_rsa_host_key\" y recargar el servicio o reiniciar el sistema antes de usar Dropbear como daemon SSH (esto borra todas las claves integradas por error en la imagen de lanzamiento) o actualizar a la \u00faltima versi\u00f3n de VyOS 1.4 o 1.5. Tenga en cuenta que esta vulnerabilidad no es exclusiva de VyOS y puede aparecer en cualquier distribuci\u00f3n de Linux basada en Debian que use Dropbear en combinaci\u00f3n con live-build, que cuenta con una protecci\u00f3n contra este comportamiento en OpenSSH, pero no con una equivalente para Dropbear."}], "id": "CVE-2025-30095", "lastModified": "2025-04-11T14:15:24.813", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 9.0, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 2.2, "impactScore": 6.0, "source": "cve@mitre.org", "type": "Secondary"}]}, "published": "2025-03-31T15:15:44.843", "references": [{"source": "cve@mitre.org", "url": "https://blog.vyos.io/vyos-project-march-2025-update"}, {"source": "cve@mitre.org", "url": "https://blog.vyos.io/vyos-stream-1.5-2025-q1"}, {"source": "cve@mitre.org", "url": "https://github.com/vyos/"}, {"source": "cve@mitre.org", "url": "https://vyos.dev/T7217"}, {"source": "cve@mitre.org", "url": "https://vyos.net/get/stream/#1.5-2025-Q1"}], "sourceIdentifier": "cve@mitre.org", "vulnStatus": "Awaiting Analysis", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-321"}], "source": "cve@mitre.org", "type": "Secondary"}]}

{}