# CVE-2013-5715: Memory corruption in n/a

> A buffer overflow in GOM Media Player allows attackers to execute arbitrary code or cause denial of service via crafted media files.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Sep 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x26f-mf78-34qq

## What is CVE-2013-5715?

CVE-2013-5715 is a critical memory corruption vulnerability in n/a, published on 9 Sep 2013. 

### Official description

Buffer overflow in Gretech GOM Media Player before 2.2.53.5169 has unspecified impact and attack vectors.

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

## Which versions are affected by CVE-2013-5715?

It affects 1 product.


Products: Gomlab Gom Player.

## How do I fix CVE-2013-5715?

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

## Is CVE-2013-5715 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-5162](https://insights.sbomify.com/CVE-2011-5162/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-1497](https://insights.sbomify.com/CVE-2009-1497/): Memory corruption in n/a (critical 9.3)
- [CVE-2017-5881](https://insights.sbomify.com/CVE-2017-5881/): Memory corruption in n/a (high 7.8)
- [CVE-2023-53875](https://insights.sbomify.com/CVE-2023-53875/): GOM Player 2.3.90.5360 Remote Code Execution via Insecure IE Component (high 7.5)
- [CVE-2023-53874](https://insights.sbomify.com/CVE-2023-53874/): GOM Player 2.3.90.5360 Buffer Overflow via Equalizer Preset Name (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5715 and fix it if it is affected.

What it is: CVE-2013-5715 is a critical memory corruption vulnerability in n/a, published on 9 Sep 2013. 
Exploitation: There is no known exploitation of CVE-2013-5715 in the wild and no public exploit code.

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-2013-5715/ (Markdown: https://insights.sbomify.com/CVE-2013-5715/index.md)
```

## Sources

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

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