# CVE-2017-13135: Null dereference in n/a

> A null pointer dereference in x265 allows attackers to cause a denial of service via memory allocation failure handling.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 16 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-13135, GHSA-c98w-gf53-9jwf, UBUNTU-CVE-2017-13135, USN-4809-1

## What is CVE-2017-13135?

CVE-2017-13135 is a high-severity vulnerability in n/a, published on 16 Nov 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

A NULL Pointer Dereference exists in VideoLAN x265, as used in libbpg 0.9.7 and other products, because the CUData::initialize function in common/cudata.cpp mishandles memory-allocation failure.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Libbpg Project Libbpg.

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

Apply the vendor's patch.

## Is CVE-2017-13135 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12447](https://insights.sbomify.com/CVE-2018-12447/): Integer overflow in n/a (high 8.8)
- [CVE-2017-13136](https://insights.sbomify.com/CVE-2017-13136/): Integer overflow in n/a (high 8.8)
- [CVE-2017-14034](https://insights.sbomify.com/CVE-2017-14034/): Memory corruption in n/a (high 8.8)
- [CVE-2017-14795](https://insights.sbomify.com/CVE-2017-14795/): Memory corruption in n/a (high 8.8)
- [CVE-2017-14796](https://insights.sbomify.com/CVE-2017-14796/): Integer overflow in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-13135 is a high-severity vulnerability in n/a, published on 16 Nov 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-13135 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-2017-13135/ (Markdown: https://insights.sbomify.com/CVE-2017-13135/index.md)
```

## Sources

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

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