A flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq checks in the forward.c:reply_query() if the reply destination address/port is used by the pending forwarded queries. However, it does not use the address/port to retrieve the exact forwarded query, substantially reducing the number of attempts an attacker on the network would have to perform to forge a reply and get it accepted by dnsmasq. This issue contrasts with RFC5452, which specifies a query's attributes that all must be used to match a reply. This flaw allows an attacker to perform a DNS Cache Poisoning attack. If chained with CVE-2020-25685 or CVE-2020-25686, the attack complexity of a successful attack is reduced. The highest threat from this vulnerability is to data integrity.
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2020-25684.json"
[
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.83"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "32"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "33"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "9.0"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "10.0"
}
]
},
{
"events": [
{
"introduced": "4.21"
},
{
"fixed": "4.21.14m"
}
]
},
{
"events": [
{
"introduced": "4.22"
},
{
"fixed": "4.22.9m"
}
]
},
{
"events": [
{
"introduced": "4.23"
},
{
"fixed": "4.23.7m"
}
]
},
{
"events": [
{
"introduced": "4.24"
},
{
"fixed": "4.24.5m"
}
]
},
{
"events": [
{
"introduced": "4.25"
},
{
"fixed": "4.25.2f"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.83"
}
]
}
]