# CVE-2011-4919: Information disclosure in mpack

> An attacker can eavesdrop on emails sent by other users using mpack, leading to information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** Yes
- **Published:** 19 Nov 2019
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-4919, GHSA-w6m4-4394-5mjr

## What is CVE-2011-4919?

CVE-2011-4919 is a high-severity vulnerability in mpack, published on 19 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mpack 1.6 has information disclosure via eavesdropping on mails sent by other users

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

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

It affects 1 product.


Products: Mpack Project Mpack.

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

Upgrade to a fixed version.

## Is CVE-2011-4919 being exploited?

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

Public exploit code:

- :unlock: CVE-2011-4919 -- mpack information disclosure demo (C) (github_poc): https://github.com/hartwork/mpacktrafficripper

## Fix prompt for AI coding agents

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

What it is: CVE-2011-4919 is a high-severity vulnerability in mpack, published on 19 Nov 2019. 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-4919 in the wild and no public exploit code.

Affected product: mpack. 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-4919/ (Markdown: https://insights.sbomify.com/CVE-2011-4919/index.md)
```

## Sources

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

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