Process crash via unchecked filter allocation
Published Nov 22, 2022 · Updated Nov 3, 2025
NULL pointer dereference in archive writing in libarchive before 3.6.2 allows attackers to crash the calling process when allocation fails. The __archive_write_allocate_filter function dereferences a calloc result to initialize filter fields without first checking whether allocation returned NULL. Triggering the crash requires a libarchive-using process to enter the archive-write path while allocation fails; code-execution impact is disputed.
Summary
What happened
NULL pointer dereference in archive writing in libarchive before 3.6.2 allows attackers to crash the calling process when allocation fails. The __archive_write_allocate_filter function dereferences a calloc result to initialize filter fields without first checking whether allocation returned NULL. Triggering the crash requires a libarchive-using process to enter the archive-write path while allocation fails; code-execution impact is disputed.
The record
- CVE
- CVE-2022-36227
- Published
- Nov 22, 2022
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 22, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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