Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1495510 - (CVE-2017-13704) CVE-2017-13704 dnsmasq: Size parameter overflow via large DNS query
CVE-2017-13704 dnsmasq: Size parameter overflow via large DNS query
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20170821,repo...
: Security
Depends On:
Blocks: 1495418
  Show dependency tree / graph
 
Reported: 2017-09-26 04:37 EDT by Andrej Nemec
Modified: 2017-10-02 10:23 EDT (History)
22 users (show)

See Also:
Fixed In Version: dnsmasq 2.78
Doc Type: If docs needed, set a value
Doc Text:
An integer underflow flaw leading to a buffer over-read was found in dnsmasq in the DNS code. An attacker could send crafted DNS packets to dnsmasq which would cause it to crash.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-09-29 01:09:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Andrej Nemec 2017-09-26 04:37:45 EDT 
It was found that if a DNS query request (qlen) is either larger than 512, or includes an EDNS0 packet size field, and the request is larger than what it specifies, then the size parameter to memset will overflow and become negative. An attacker could use this for a remote denial of service attack.

References:

http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2017q3/011729.html

Upstream patch:

http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=63437ffbb58837b214b4b92cb1c54bc5f3279928
Comment 1 Tomas Hoger 2017-09-26 04:40:59 EDT 
Upstream CHANGELOG notes this issue is a regression introduced in dnsmasq version  2.77 and is getting fixed in version 2.78.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.