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

> A NULL pointer dereference in the xar library allows attackers to cause a denial of service via crafted archive files.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2018-17094, DEBIAN-CVE-2017-11124, GHSA-6jc8-h4qw-9892

## What is CVE-2017-11124?

CVE-2017-11124 is a critical vulnerability in n/a, published on 10 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libxar.so in xar 1.6.1 has a NULL pointer dereference in the xar_unserialize function in archive.c.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Xar Project Xar.

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

Apply the vendor's patch.

## Is CVE-2017-11124 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11125](https://insights.sbomify.com/CVE-2017-11125/): Null dereference in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11124 is a critical vulnerability in n/a, published on 10 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11124 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-11124/ (Markdown: https://insights.sbomify.com/CVE-2017-11124/index.md)
```

## Sources

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

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