CVE-2024-4871

{"id": "CVE-2024-4871", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "secalert@redhat.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.8, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 1.6}]}, "published": "2024-05-14T16:17:37.163", "references": [{"url": "https://access.redhat.com/errata/RHBA-2024:4589", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/security/cve/CVE-2024-4871", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2278627", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/security/cve/CVE-2024-4871", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2278627", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-322"}]}], "descriptions": [{"lang": "en", "value": "A vulnerability was found in Satellite. When running a remote execution job on a host, the host's SSH key is not being checked. When the key changes, the Satellite still connects it because it uses \"-o StrictHostKeyChecking=no\". This flaw can lead to a man-in-the-middle attack (MITM), denial of service, leaking of secrets the remote execution job contains, or other issues that may arise from the attacker's ability to forge an SSH key. This issue does not directly allow unauthorized remote execution on the Satellite, although it can leak secrets that may lead to it."}, {"lang": "es", "value": "Se encontr\u00f3 una vulnerabilidad en Satellite. Cuando se ejecuta un trabajo de ejecuci\u00f3n remota en un host, no se verifica la clave SSH del host. Cuando la clave cambia, el Sat\u00e9lite a\u00fan lo conecta porque usa \"-o StrictHostKeyChecking=no\". Esta falla puede provocar un ataque de intermediario (MITM), denegaci\u00f3n de servicio, filtraci\u00f3n de secretos que contiene el trabajo de ejecuci\u00f3n remota u otros problemas que pueden surgir de la capacidad del atacante para falsificar una clave SSH. Este problema no permite directamente la ejecuci\u00f3n remota no autorizada en el Sat\u00e9lite, aunque puede filtrar secretos que pueden conducir a ello."}], "lastModified": "2024-11-21T09:43:45.893", "sourceIdentifier": "secalert@redhat.com"}