Remote service crash via prefixless SERVER command
Published Jun 15, 2020 · Updated Aug 4, 2024
Out-of-bounds access in ngIRCd before 26~rc2 allows remote attackers posing as a peer IRC server to crash the service. IRC_SERVER passed an absent Req->prefix to Client_Search instead of rejecting the SERVER command, and a following NJOIN reached an invalid iconv conversion. The path is limited to server-to-server traffic and was demonstrated with iconv enabled; the reported consequence is a process crash.
Summary
What happened
Out-of-bounds access in ngIRCd before 26~rc2 allows remote attackers posing as a peer IRC server to crash the service. IRC_SERVER passed an absent Req->prefix to Client_Search instead of rejecting the SERVER command, and a following NJOIN reached an invalid iconv conversion. The path is limited to server-to-server traffic and was demonstrated with iconv enabled; the reported consequence is a process crash.
The record
- CVE
- CVE-2020-14148
- Published
- Jun 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 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
- Minimized server-to-server crash inputproof of concept · demonstrated
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