# CVE-2011-3625: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause a crash in MPlayer/SMPlayer by tricking users into opening a malicious SAMI subtitle file.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-3625, GHSA-fv2g-q5cc-8667

## What is CVE-2011-3625?

CVE-2011-3625 is a critical memory corruption vulnerability in n/a, published on 11 Jun 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in the sub_read_line_sami function in subreader.c in MPlayer, as used in SMPlayer 0.6.9, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long string in a SAMI subtitle file.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Mplayer2 Mplayer2, Ricardo Villalba Smplayer.

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

Upgrade to a fixed version.

## Is CVE-2011-3625 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-3625 exists.

Public exploit code:

- MPlayer SAMI Subtitle File Buffer Overflow (metasploit)
- MPlayer - '.SAMI' Subtitle File Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3625 is a critical memory corruption vulnerability in n/a, published on 11 Jun 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-3625 exists.

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

## Sources

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

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