# CVE-2011-5282: Information disclosure in mIRC

> An attacker can leak message content from mIRC due to improper handling of outbound message chopping.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2020
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8gv2-3g44-v322

## What is CVE-2011-5282?

CVE-2011-5282 is a medium-severity vulnerability in mIRC, published on 21 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mIRC prior to 7.22 has a message leak because chopping of outbound messages is mishandled.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2011-5282?

It affects 1 product.


Products: Mirc Mirc.

## How do I fix CVE-2011-5282?

No fix has been published for CVE-2011-5282 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-5282 being exploited?

There is no known exploitation of CVE-2011-5282 in the wild and no public exploit code.

## Other vulnerabilities in mIRC

- [CVE-2008-4449](https://insights.sbomify.com/CVE-2008-4449/): Memory corruption in n/a (critical 9.3)
- [CVE-2003-1336](https://insights.sbomify.com/CVE-2003-1336/): Memory corruption in n/a (critical 9.3)
- [CVE-2019-6453](https://insights.sbomify.com/CVE-2019-6453/): Command injection in n/a (high 8.1)
- [CVE-2008-7314](https://insights.sbomify.com/CVE-2008-7314/): Denial of service in mIRC (high 7.5)
- [CVE-2007-4402](https://insights.sbomify.com/CVE-2007-4402/): Command injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5282 and fix it if it is affected.

What it is: CVE-2011-5282 is a medium-severity vulnerability in mIRC, published on 21 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-5282 in the wild and no public exploit code.

Affected product: mIRC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-5282/ (Markdown: https://insights.sbomify.com/CVE-2011-5282/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-5282
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-5282
- OSV: https://osv.dev/vulnerability/CVE-2011-5282

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-5282/
Summaries are generated and may contain mistakes; the official description above is the record.