Application crash via unchecked null archive basename
Published Nov 14, 2022 · Updated May 1, 2025
NULL pointer dereference in GNOME Nautilus 42.2 allows local users to crash the file manager by pasting a crafted ZIP archive. The get_basename path calls UTF-8 validation on a null value returned when an archive member lacks a usable basename, rather than rejecting that missing name. Exploitation requires a local session and an intentional paste operation; the consequence is termination of the affected graphical file-manager process.
Summary
What happened
NULL pointer dereference in GNOME Nautilus 42.2 allows local users to crash the file manager by pasting a crafted ZIP archive. The get_basename path calls UTF-8 validation on a null value returned when an archive member lacks a usable basename, rather than rejecting that missing name. Exploitation requires a local session and an intentional paste operation; the consequence is termination of the affected graphical file-manager process.
The record
- CVE
- CVE-2022-37290
- Published
- Nov 14, 2022
- Updated
- May 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 14, 2022CVE publishedPublication date reported by the CVE source.
- May 1, 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.
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
- GNOME Nautilus issue 2376 reproductionproof of concept · unverified
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