# CVE-2023-31439: An issue was discovered in systemd 253.


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Jun 2023
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2023-31439, GHSA-mvwm-rcrw-pr2j

## What is CVE-2023-31439?

CVE-2023-31439 is a medium-severity vulnerability in Systemd Project Systemd, published on 13 Jun 2023. 

### Official description

An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2023-31439?

It affects 1 product.


Products: Systemd Project Systemd.

## How do I fix CVE-2023-31439?

No fix has been published for CVE-2023-31439 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-31439 being exploited?

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

## Other vulnerabilities in Systemd Project Systemd

- [CVE-2015-7510](https://insights.sbomify.com/CVE-2015-7510/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-1000082](https://insights.sbomify.com/CVE-2017-1000082/): Privilege escalation in n/a (critical 9.8)
- [CVE-2016-10156](https://insights.sbomify.com/CVE-2016-10156/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-9445](https://insights.sbomify.com/CVE-2017-9445/): Memory corruption in n/a (high 7.5)
- [CVE-2017-9217](https://insights.sbomify.com/CVE-2017-9217/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31439 and fix it if it is affected.

What it is: CVE-2023-31439 is a medium-severity vulnerability in Systemd Project Systemd, published on 13 Jun 2023. 
Exploitation: There is no known exploitation of CVE-2023-31439 in the wild and no public exploit code.

Affected product: Systemd Project Systemd. 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-2023-31439/ (Markdown: https://insights.sbomify.com/CVE-2023-31439/index.md)
```

## Sources

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

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