Memory exhaustion via unsanitized history path rendering
Published Jan 18, 2022 · Updated Apr 23, 2025
Denial of service in OnionShare before 2.5 allows remote attackers to exhaust desktop memory through a crafted history path. The history item widget passes the path parameter into Qt image rendering without first sanitizing it to plain text, so roughly 20 input bytes can allocate about 2 GB repeatedly. The attacker must know the onion address and use a public service or valid private-service authentication, and a user must display history; success drives the hosting desktop process out of memory.
Summary
What happened
Denial of service in OnionShare before 2.5 allows remote attackers to exhaust desktop memory through a crafted history path. The history item widget passes the path parameter into Qt image rendering without first sanitizing it to plain text, so roughly 20 input bytes can allocate about 2 GB repeatedly. The attacker must know the onion address and use a public service or valid private-service authentication, and a user must display history; success drives the hosting desktop process out of memory.
The record
- CVE
- CVE-2022-21688
- Published
- Jan 18, 2022
- Updated
- Apr 23, 2025
- Vendor
- OnionShare
- Product
- OnionShare
- Classifications
- CWE-125, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=< 2.5
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.
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