CVE-2017-9109
moderate-risk
Published 2020-06-18
An issue was discovered in adns before 1.5.2. It fails to ignore apparent answers before the first RR that was found the first time. when this is fixed, the second answer scan finds the same RRs at the first. Otherwise, adns can be confused by interleaving answers for the CNAME target, with the CNAME itself. In that case the answer data structure (on the heap) can be overrun. With this fixed, it prefers to look only at the answer RRs which come after the CNAME, which is at least arguably correct.
Do I need to act?
-
0.89% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
9
CVSS 9.8/10
Critical
NETWORK
/ LOW complexity
Affected Vendors
References (12)
Third Party Advisory
http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=adns.git
Third Party Advisory
http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=adns.git
45
/ 100
moderate-risk
Severity
32/34 · Critical
Exploitability
3/34 · Minimal
Exposure
10/34 · Low