Sealed log forgery via one-way epoch validation
Published Jun 13, 2023 · Updated Aug 2, 2024
Improper journal integrity verification in systemd 198 through 254 allows attackers to forge sealed past log entries undetected. journalctl --verify rejects newer entries sealed with an older epoch key but fails to reject older entries sealed with a newer key, allowing the current key to authenticate backdated modifications. Exploitation requires control of the host and its current sealing key; the result is undetected alteration of historical journal evidence, not code execution or service interruption.
Summary
What happened
Improper journal integrity verification in systemd 198 through 254 allows attackers to forge sealed past log entries undetected. journalctl --verify rejects newer entries sealed with an older epoch key but fails to reject older entries sealed with a newer key, allowing the current key to authenticate backdated modifications. Exploitation requires control of the host and its current sealing key; the result is undetected alteration of historical journal evidence, not code execution or service interruption.
The record
- CVE
- CVE-2023-31439
- Published
- Jun 13, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-354, T1070.002
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 13, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- KASTEL Journald attack reproducerfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo