# CVE-2017-8313: Information disclosure in VLC

> Attackers can read memory or crash VLC via crafted subtitles due to a heap out-of-bound read in the JSS parser.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-8313, GHSA-x47q-49w5-cg3q, UBUNTU-CVE-2017-8313

## What is CVE-2017-8313?

CVE-2017-8313 is a medium-severity vulnerability in Videolan Vlc Media Player, published on 23 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Heap out-of-bound read in ParseJSS in VideoLAN VLC before 2.2.5 due to missing check of string termination allows attackers to read data beyond allocated memory and potentially crash the process via a crafted subtitles file.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2017-8313?

It affects 1 product.


Products: Videolan Vlc Media Player.

## How do I fix CVE-2017-8313?

Upgrade to a fixed version.

## Is CVE-2017-8313 being exploited?

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

## Other vulnerabilities in Videolan Vlc Media Player

- [CVE-2008-0296](https://insights.sbomify.com/CVE-2008-0296/): Memory corruption in n/a (critical 10.0)
- [CVE-2023-47359](https://insights.sbomify.com/CVE-2023-47359/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-12874](https://insights.sbomify.com/CVE-2019-12874/): Use after free in n/a (critical 9.8)
- [CVE-2017-10699](https://insights.sbomify.com/CVE-2017-10699/): Memory corruption in n/a (critical 9.8)
- [CVE-2013-1868](https://insights.sbomify.com/CVE-2013-1868/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8313 and fix it if it is affected.

What it is: CVE-2017-8313 is a medium-severity vulnerability in Videolan Vlc Media Player, published on 23 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-8313 in the wild and no public exploit code.

Affected product: Videolan Vlc Media Player. 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-2017-8313/ (Markdown: https://insights.sbomify.com/CVE-2017-8313/index.md)
```

## Sources

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

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