A flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq checks in forward.c:reply_query(), wh…
A flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq checks in forward.c:reply_query(), which is the forwarded query that matches the reply, by only using a weak hash of the query name. Due to the weak hash (CRC32 when dnsmasq is compiled without DNSSEC, SHA-1 when it is) this flaw allows an off-path attacker to find several different domains all having the same hash, substantially reducing the number of attempts they would have to perform to forge a reply and get it accepted by dnsmasq. This is in contrast with RFC5452, which specifies that the query name is one of the attributes of a query that must be used to match a reply. This flaw could be abused to perform a DNS Cache Poisoning attack. If chained with CVE-2020-25684 the attack complexity of a successful attack is reduced. The highest threat from this vulnerability is to data integrity.
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
https://cwe.mitre.org/data/definitions/326.html →Open in CWE collection →An attacker, armed with the cipher text and the encryption algorithm used, performs an exhaustive (brute force) search on the key space to determine the key that decrypts the cipher text to obtain the plaintext.
https://capec.mitre.org/data/definitions/20.html →Open in CAPEC collection →In this attack, some asset (information, functionality, identity, etc.) is protected by a finite secret value. The attacker attempts to gain access to this asset by using trial-and-error to exhaustively explore all the possible secret values in the hope of finding the secret (or a value that is functionally equivalent) that will unlock the asset.
https://capec.mitre.org/data/definitions/112.html →Open in CAPEC collection →An adversary engages in activities to decipher and/or decode protocol information for a network or application communication protocol used for transmitting information between interconnected nodes or systems on a packet-switched data network. While this type of analysis involves the analysis of a networking protocol inherently, it does not require the presence of an actual or physical network.
https://capec.mitre.org/data/definitions/192.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked | |
| dnsmasq | Tracked |