Persistent client crash via malformed resource identifier
Published Mar 11, 2022 · Updated Apr 23, 2025
Denial of service in Wire iOS before 3.95 allows remote authenticated users to crash the client via a malformed resource identifier. The wire-ios-transport logging redaction code attempts to remove sensitive tokens from the malformed identifier but throws a Swift exception instead. A Wire user can send the identifier without recipient interaction; the persisted item triggers a crash on each launch, while the broader Wire service remains available.
Summary
What happened
Denial of service in Wire iOS before 3.95 allows remote authenticated users to crash the client via a malformed resource identifier. The wire-ios-transport logging redaction code attempts to remove sensitive tokens from the malformed identifier but throws a Swift exception instead. A Wire user can send the identifier without recipient interaction; the persisted item triggers a crash on each launch, while the broader Wire service remains available.
The record
- CVE
- CVE-2022-23625
- Published
- Mar 11, 2022
- Updated
- Apr 23, 2025
- Vendor
- Wire Swiss GmbH
- Product
- Wire iOS
- Classifications
- CWE-755, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 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=< 3.95
What conditions does exploitation require?
What is affected?
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.
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