Daemon crash via unreleased CMAC packet allocations
Published Jun 24, 2020 · Updated Aug 4, 2024
Memory leak in ntpd 4.2.8p11 through 4.2.8p14 and 4.3.97 through 4.3.100 allows remote authenticated users to crash the daemon. For each packet using a CMAC key ID, CMAC cleanup fails to fully remove the CMAC data structure, leaving a small allocation unreleased. Exploitation requires a configured CMAC algorithm and associated key in ntp.keys; repeated authenticated packets exhaust memory until ntpd aborts.
Summary
What happened
Memory leak in ntpd 4.2.8p11 through 4.2.8p14 and 4.3.97 through 4.3.100 allows remote authenticated users to crash the daemon. For each packet using a CMAC key ID, CMAC cleanup fails to fully remove the CMAC data structure, leaving a small allocation unreleased. Exploitation requires a configured CMAC algorithm and associated key in ntp.keys; repeated authenticated packets exhaust memory until ntpd aborts.
The record
- CVE
- CVE-2020-15025
- Published
- Jun 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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