Client crash via oversized server-sent nickname
Published Jan 23, 2020 · Updated Aug 7, 2024
Denial of service in mIRC before 6.35 allows remote attackers to crash the client via a long nickname sent by an IRC server. mIRC Company Limited has not disclosed which nickname-processing routine mishandles the oversized value or the underlying operation. A target must connect to a server that supplies a nickname hundreds of characters long; successful exploitation terminates the client session.
Summary
What happened
Denial of service in mIRC before 6.35 allows remote attackers to crash the client via a long nickname sent by an IRC server. mIRC Company Limited has not disclosed which nickname-processing routine mishandles the oversized value or the underlying operation. A target must connect to a server that supplies a nickname hundreds of characters long; successful exploitation terminates the client session.
The record
- CVE
- CVE-2008-7314
- Published
- Jan 23, 2020
- Updated
- Aug 7, 2024
- Vendor
- mIRC Company Limited
- Product
- mIRC
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 7, 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=before 6.35
What conditions does exploitation require?
What is affected?
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