Credential capture or crash via file URI
Published Jun 17, 2022 · Updated Aug 3, 2024
Improper URI validation in Electrum 2.1 through 4.2.1 allows attackers to trigger local file reads through crafted BIP70 payment requests. The paymentrequest.py handler accepts an attacker-controlled file URI in the r parameter, opens the referenced path in read mode, and parses returned data as protobuf. Scanning a malicious QR code or pasting its text is required; /dev/zero exhausts memory on Linux or macOS, while a Windows UNC path can expose an SMB authentication token.
Summary
What happened
Improper URI validation in Electrum 2.1 through 4.2.1 allows attackers to trigger local file reads through crafted BIP70 payment requests. The paymentrequest.py handler accepts an attacker-controlled file URI in the r parameter, opens the referenced path in read mode, and parses returned data as protobuf. Scanning a malicious QR code or pasting its text is required; /dev/zero exhausts memory on Linux or macOS, while a Windows UNC path can expose an SMB authentication token.
The record
- CVE
- CVE-2022-31246
- Published
- Jun 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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.
Weakness, pattern, technique
Public exploit references
- BIP70 file URI payment-request examplesproof of concept · demonstrated
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