Daemon crash via oversized management-address TLV
Published Jan 28, 2020 · Updated Aug 6, 2024
Buffer overflow in lldpd 0.6.0 through 0.7.18 allows remote attackers on the local network to crash the daemon with a crafted LLDP packet. The lldp_decode management-address TLV path trusts its one-byte address length and copies that many bytes into a smaller fixed static buffer. No authentication or user interaction is required, but the parser is unprivileged and chrooted, so code execution requires disabled hardening.
Summary
What happened
Buffer overflow in lldpd 0.6.0 through 0.7.18 allows remote attackers on the local network to crash the daemon with a crafted LLDP packet. The lldp_decode management-address TLV path trusts its one-byte address length and copies that many bytes into a smaller fixed static buffer. No authentication or user interaction is required, but the parser is unprivileged and chrooted, so code execution requires disabled hardening.
The record
- CVE
- CVE-2015-8011
- Published
- Jan 28, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
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
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