How many CVEs have patched is_answertarget_allowed?

2 published CVEs changed is_answertarget_allowed in debian/bind9, in 2 distinct patches totalling 10 changed lines, between 2016 and 2019.

What is the latest CVE that changed is_answertarget_allowed?

CVE-2017-3137 (A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME), published 2019-01-16, changed lines 6896 to 6921 of lib/dns/resolver.c.

How does is_answertarget_allowed compare to the rest of debian/bind9?

debian/bind9 has 13 CVEs with a located fix in total; 2 of them changed is_answertarget_allowed.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

debian/bind9

Function

is_answertarget_allowed

Name: is_answertarget_allowed in debian/bind9: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

lib/dns/resolver.c

Last patched January 16, 2019

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

10

Lines changed

Added plus removed

2016–2019

Years

By CVE publication date

Overview

is_answertarget_allowed in debian/bind9 was changed by 2 published CVE fixes between 2016 and 2019, in 2 distinct patches that added or removed 10 lines in total.

debian/bind9 has 13 CVEs with a located fix in total, so 15% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed is_answertarget_allowed, newest first, with the lines each fix touched.

A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME
CVE-2017-3137 · lines 6896–6921 · +4 −2 in 2 hunks
High · CVSS 7.5
EPSS 9.0%2019-01-16
CVE-2016-8864
CVE-2016-8864 · lines 7113–7114 · +2 −2
High · CVSS 7.5
EPSS 38.7%2016-11-02

Get an alert when the next CVE fix lands in debian/bind9, with the patched functions.

Monitor bind9 CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in debian/bind9 changed by the most CVE fixes.

answer_response4 CVEs · lib/dns/resolver.c dns_message_checksig1 CVEs · lib/dns/message.c do_cancel1 CVEs · lib/dns/dispatch.c dns_dispatch_getnext1 CVEs · lib/dns/dispatch.c exit_check1 CVEs · bin/named/client.c client_start1 CVEs · bin/named/client.c

All patched functions in debian/bind9

Frequently asked questions

Common questions about CVE fixes to is_answertarget_allowed.

How many CVEs have patched is_answertarget_allowed?: 2 published CVEs changed is_answertarget_allowed in debian/bind9, in 2 distinct patches totalling 10 changed lines, between 2016 and 2019.
What is the latest CVE that changed is_answertarget_allowed?: CVE-2017-3137 (A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME), published 2019-01-16, changed lines 6896 to 6921 of lib/dns/resolver.c.
How does is_answertarget_allowed compare to the rest of debian/bind9?: debian/bind9 has 13 CVEs with a located fix in total; 2 of them changed is_answertarget_allowed.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track debian/bind9 CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing