Outbound message disclosure via flawed message chopping
Published Jan 21, 2020 · Updated Aug 7, 2024
Information disclosure in mIRC before 7.22 allows remote attackers to receive a subsequent outbound message after an earlier message is chopped. The outbound-message chopping logic mishandles message boundaries in a specific context and leaks the message that follows. Reaching the flaw requires mIRC to chop an outgoing message in that undisclosed context; the reported consequence is exposure of the subsequent message only.
Summary
What happened
Information disclosure in mIRC before 7.22 allows remote attackers to receive a subsequent outbound message after an earlier message is chopped. The outbound-message chopping logic mishandles message boundaries in a specific context and leaks the message that follows. Reaching the flaw requires mIRC to chop an outgoing message in that undisclosed context; the reported consequence is exposure of the subsequent message only.
The record
- CVE
- CVE-2011-5282
- Published
- Jan 21, 2020
- Updated
- Aug 7, 2024
- Vendor
- mIRC Company Limited
- Product
- mIRC
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 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=prior to 7.22
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