Service crash via rr_decode memory leak
Published Mar 24, 2020 · Updated Aug 4, 2024
Resource exhaustion in Videolabs libmicrodns 0.1.0 allows remote attackers to crash a consuming service with repeated mDNS messages. rr_decode allocates entry->name, but rr_read returns after a type-specific parser rejects an invalid SRV, PTR, TXT, AAAA, or A record without freeing that buffer. No authentication or user interaction is required, and repetition exhausts process memory until the embedding service crashes.
Summary
What happened
Resource exhaustion in Videolabs libmicrodns 0.1.0 allows remote attackers to crash a consuming service with repeated mDNS messages. rr_decode allocates entry->name, but rr_read returns after a type-specific parser rejects an invalid SRV, PTR, TXT, AAAA, or A record without freeing that buffer. No authentication or user interaction is required, and repetition exhausts process memory until the embedding service crashes.
The record
- CVE
- CVE-2020-6079
- Published
- Mar 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Videolabs
- Product
- libmicrodns
- Classifications
- CWE-401, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Videolabs libmicrodns 0.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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