Disputed service interruption via benchmark memory leak
Published Feb 27, 2024 · Updated Aug 29, 2024
A disputed memory leak in Atheme IRC Services 7.2.12 allows attackers to exhaust memory through the crypto-benchmark utility. The utility duplicates an option string, then returns from its argument loop without freeing that allocation when a help or error branch is taken. Upstream and Debian state that the command-line utility exits immediately, so the allocation is reclaimed and the daemon is not remotely exposed; no service interruption is established.
Summary
What happened
A disputed memory leak in Atheme IRC Services 7.2.12 allows attackers to exhaust memory through the crypto-benchmark utility. The utility duplicates an option string, then returns from its argument loop without freeing that allocation when a help or error branch is taken. Upstream and Debian state that the command-line utility exits immediately, so the allocation is reclaimed and the daemon is not remotely exposed; no service interruption is established.
The record
- CVE
- CVE-2024-27508
- Published
- Feb 27, 2024
- Updated
- Aug 29, 2024
- Vendor
- Atheme Development Group
- Product
- Atheme IRC Services
- Classifications
- CWE-401
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 27, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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=7.2.12
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