Lucene search
K

A flaw was found in dnsmasq in versions before 2.85. When configured to use a specific server for a given network interface dnsmasq uses a fixed port while forwarding queries. An attacker on the network able to find the outgoing port used by dnsmasq only needs to guess the random transmission ID to forge a reply and get it accepted by dnsmasq. This flaw makes a DNS Cache Poisoning attack much easier. The highest threat from this vulnerability is to data integrity.

🗓️ 23 Apr 2021 07:00:00Reported by MicrosoftType 
mscve
 mscve
🔗 msrc.microsoft.com👁 2 Views

Dnsmasq flaw before 2.85 allows cache poisoning via fixed port and guessed transaction identifier.

Related
Detection

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

10 Mar 2023 08:00Current
7High risk
Vulners AI Score7
CVSS 3.14
CVSS 24.3
EPSS0.00044
SSVC
2