Low [CVE-2025-8283] Netavark: podman: netavark may resolve hostnames to unexpected hosts
This low-severity Red Hat Linux advisory covers CVE-2025-8283 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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. This vulnerability has been rated as having a Low security impact by the Red Hat Product Security team.
For an attack to be successful, the attacker needs to have control over the domains used into the host's resolv.conf and have a prior knowledge about the hostnames and connections used by the running containers.
Additionally, the attacker does not have full control over the amount or sensitivity of data sent by the container to the attacker controlled host and TLS validations may avoid the container to connect to the malicious domain. Red Hat severity: Low — CVSS 3.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).
Weakness: CWE-15.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Mitigation checklist
- As a proactive mitigation, configure containers to have hostnames formatted as <name>.dns.podman. This specific naming convention will prevent aardvark-dns from forwarding these queries to external search domains, thereby reducing potential exposure or unexpected network behavior associated with such queries.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.