Application injection via unvalidated DNS resolver output
Published Nov 10, 2021 · Updated May 5, 2025
Improper hostname validation in uClibc and uClibc-ng before 1.0.39 allows context-dependent attackers to inject resolver output. The DNS resolver functions accept decoded answer and reverse-lookup names without rejecting nonprintable or disallowed characters, so crafted names can be misread or passed unchanged to consuming applications. Exploitation requires an attacker-controlled lookup or DNS response; the resulting impact depends on the consumer and includes cache poisoning, XSS, SQL injection, code execution, or a crash.
Summary
What happened
Improper hostname validation in uClibc and uClibc-ng before 1.0.39 allows context-dependent attackers to inject resolver output. The DNS resolver functions accept decoded answer and reverse-lookup names without rejecting nonprintable or disallowed characters, so crafted names can be misread or passed unchanged to consuming applications. Exploitation requires an attacker-controlled lookup or DNS response; the resulting impact depends on the consumer and includes cache poisoning, XSS, SQL injection, code execution, or a crash.
The record
- CVE
- CVE-2021-43523
- Published
- Nov 10, 2021
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 2021CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted DNS hostname examplesproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo