CVE-2025-8283

{"id": "CVE-2025-8283", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "secalert@redhat.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.7, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 2.2}]}, "published": "2025-07-28T19:15:43.957", "references": [{"url": "https://access.redhat.com/security/cve/CVE-2025-8283", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2383941", "source": "secalert@redhat.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-15"}]}], "descriptions": [{"lang": "en", "value": "A vulnerability was found in the netavark package, a network stack for containers used with Podman. Due to dns.podman search domain being removed, netavark may return external servers if a valid A/AAAA record is sent as a response. When creating a container with a given name, this name will be used as the hostname for the container itself, as the podman's search domain is not added anymore the container is using the host's resolv.conf, and the DNS resolver will try to look into the search domains contained on it. If one of the domains contain a name with the same hostname as the running container, the connection will forward to unexpected external servers."}, {"lang": "es", "value": "Se encontr\u00f3 una vulnerabilidad en el paquete netavark, una pila de red para contenedores utilizados con Podman. Debido a la eliminaci\u00f3n del dominio de b\u00fasqueda dns.podman, netavark podr\u00eda devolver servidores externos si se env\u00eda un registro A/AAAA v\u00e1lido como respuesta. Al crear un contenedor con un nombre determinado, este se usar\u00e1 como nombre de host del contenedor. Dado que el dominio de b\u00fasqueda de Podman ya no se agrega, el contenedor utiliza el archivo resolv.conf del host y el solucionador DNS intentar\u00e1 buscar en los dominios de b\u00fasqueda que contiene. Si uno de los dominios contiene el mismo nombre de host que el contenedor en ejecuci\u00f3n, la conexi\u00f3n se redireccionar\u00e1 a servidores externos inesperados."}], "lastModified": "2025-07-29T14:14:29.590", "sourceIdentifier": "secalert@redhat.com"}