Service interruption via DHCPv4 client-ID memory leak
Published Feb 10, 2020 · Updated Aug 4, 2024
Memory leak in openSUSE wicked 0.6.55 and earlier allows remote attackers to interrupt service via DHCPv4 packets with a different client ID. The ni_dhcp4_fsm_process_dhcp4_packet function fails to release memory while processing packets whose client ID differs from the local client. No authentication or user interaction is required; repeated packets consume process memory and interrupt the DHCPv4 service.
Summary
What happened
Memory leak in openSUSE wicked 0.6.55 and earlier allows remote attackers to interrupt service via DHCPv4 packets with a different client ID. The ni_dhcp4_fsm_process_dhcp4_packet function fails to release memory while processing packets whose client ID differs from the local client. No authentication or user interaction is required; repeated packets consume process memory and interrupt the DHCPv4 service.
The record
- CVE
- CVE-2020-7217
- Published
- Feb 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 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?
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