# CVE-2022-39837: Null dereference in n/a

> A crafted DLT file causes a NULL pointer dereference in the dlt-daemon, leading to a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/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:** 24 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** DEBIAN-CVE-2022-39837, GHSA-6855-rwxj-9xgr, UBUNTU-CVE-2022-39837

## What is CVE-2022-39837?

CVE-2022-39837 is a medium-severity vulnerability in n/a, published on 24 Oct 2022. 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

An issue was discovered in Connected Vehicle Systems Alliance (COVESA) dlt-daemon through 2.18.8. Due to a faulty DLT file parser, a crafted DLT file that crashes the process can be created. This is due to missing validation checks. There is a NULL pointer dereference,

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2022-39837?

It affects 1 product.


Products: Genivi Diagnostic Log and Trace.

## How do I fix CVE-2022-39837?

Upgrade to a fixed version.

## Is CVE-2022-39837 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39837 exists.

## Other vulnerabilities in n/a

- [CVE-2021-29507](https://insights.sbomify.com/CVE-2021-29507/): dlt-daemon could crash if there is special character in dlt.conf (medium 5.7)
- [CVE-2022-39836](https://insights.sbomify.com/CVE-2022-39836/): Memory corruption in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39837 and fix it if it is affected.

What it is: CVE-2022-39837 is a medium-severity vulnerability in n/a, published on 24 Oct 2022. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39837 exists.

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

## Sources

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

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