Local process crash via freed libtar pointer
Published Dec 19, 2022 · Updated Apr 17, 2025
Use-after-free in libtar on openEuler 20.03 LTS SP1, 20.03 LTS SP3, and 22.03 LTS allows local users to crash archive-listing processes. In libtar.c, list() calls tar_close(), which frees the TAR object, then passes t->th_buf from that freed object to free_longlink_longname(). Exploitation requires local execution of the affected archive-listing path and interrupts only that process; no data disclosure or modification is reported.
Summary
What happened
Use-after-free in libtar on openEuler 20.03 LTS SP1, 20.03 LTS SP3, and 22.03 LTS allows local users to crash archive-listing processes. In libtar.c, list() calls tar_close(), which frees the TAR object, then passes t->th_buf from that freed object to free_longlink_longname(). Exploitation requires local execution of the affected archive-listing path and interrupts only that process; no data disclosure or modification is reported.
The record
- CVE
- CVE-2021-33640
- Published
- Dec 19, 2022
- Updated
- Apr 17, 2025
- Vendor
- openEuler
- Product
- openEuler
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 17, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=libtar 1.2.20-19
- Affected versionversion=libtar 1.2.20-21
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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