FedoraOperating system · Fedoraproject

CVE-2017-9107

HIGH · 7.5 CVSS v3.1 Published 2020-06-18
Fix available
A fix is available. Upgrade to 1.5.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer over-read vulnerability in adns versions before 1.5.2 allows the qdparselabel function to read beyond the input buffer when parsing a domain name ending with a backslash (\) while the adns_qf_quoteok_query flag is set. This causes the parser to consume arbitrary heap data as if it were escape sequences, potentially leading to denial of service via crash or memory exhaustion.

MitigationUpgrade adns to version 1.5.2 or later to patch the buffer over-read in the qdparselabel function. If upgrading is not immediately feasible, avoid using the adns_qf_quoteok_query flag with untrusted domain input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 31= 32
AdnsApplication
Affected:< 1.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if adns library is installed
    On Fedora: rpm -qa | grep -i adns. On Debian/Ubuntu: dpkg -l | grep -i adns. Or check for libadns shared library: ls -la /usr/lib*/libadns*
    Affected if adns package or library files are present on the system
  2. Determine installed adns version
    Run: rpm -q adns (Fedora) or dpkg -s adns (Debian). Or check library version: strings /usr/lib*/libadns.so.1 2>/dev/null | grep -i version
    Affected if Version is found to be lower than 1.5.2 or no version is returned (indicating old/unpatched package)
  3. Identify applications using adns_qf_quoteok_query flag
    Search application source code or binaries for the flag: grep -r "adns_qf_quoteok_query" /path/to/your/applications. Also check configuration files for any references to this flag.
    Affected if Applications or services use adns with the adns_qf_quoteok_query flag enabled when parsing external domain input
  4. Verify Fedora version if applicable
    Check running Fedora release: cat /etc/fedora-release or cat /etc/redhat-release
    Affected if System runs Fedora 31 or Fedora 32 and has adns installed

A system is affected if adns version is present and is lower than 1.5.2 AND any application using adns parses domain names with the adns_qf_quoteok_query flag enabled against untrusted input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.5.2 or later
Fixed in 1.5.2
Interim mitigation

Upgrade adns to version 1.5.2 or later to patch the buffer over-read in the qdparselabel function. If upgrading is not immediately feasible, avoid using the adns_qf_quoteok_query flag with untrusted domain input.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9107 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-9107 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data