Bug 1849784 (CVE-2017-9107) - CVE-2017-9107 adns: out-of-bounds read when a domain ends with backslash
Summary: CVE-2017-9107 adns: out-of-bounds read when a domain ends with backslash
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2017-9107
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1849785
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-22 19:37 UTC by Guilherme de Almeida Suckevicz
Modified: 2020-06-22 23:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-22 23:20:41 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-06-22 19:37:55 UTC
An issue was discovered in adns before 1.5.2. It overruns reading a buffer if a domain ends with backslash. If the query domain ended with \, and adns_qf_quoteok_query was specified, qdparselabel would read additional bytes from the buffer and try to treat them as the escape sequence. It would depart the input buffer and start processing many bytes of arbitrary heap data as if it were the query domain. Eventually it would run out of input or find some other kind of error, and declare the query domain invalid. But before then it might outrun available memory and crash. In principle this could be a denial of service attack.

Reference:
https://www.chiark.greenend.org.uk/pipermail/adns-announce/2020/000004.html

Comment 1 Guilherme de Almeida Suckevicz 2020-06-22 19:38:08 UTC
Created adns tracking bugs for this issue:

Affects: fedora-all [bug 1849785]

Comment 2 Product Security DevOps Team 2020-06-22 23:20:41 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.