Token-minting authority theft via reordered outputs
Published Apr 28, 2020 · Updated Aug 4, 2024
Improper transaction construction in Electron Cash SLP Edition before 3.6.2 allows attackers to obtain token-minting authority. The Mint Tool adds the baton input after coin selection instead of marking it mandatory, allowing BIP LI01 sorting to swap the baton and token receiver outputs. The flaw is reached when a token creator uses the Mint Tool; the resulting transaction can grant another party new-token issuance or permanently destroy future minting capability.
Summary
What happened
Improper transaction construction in Electron Cash SLP Edition before 3.6.2 allows attackers to obtain token-minting authority. The Mint Tool adds the baton input after coin selection instead of marking it mandatory, allowing BIP LI01 sorting to swap the baton and token receiver outputs. The flaw is reached when a token creator uses the Mint Tool; the resulting transaction can grant another party new-token issuance or permanently destroy future minting capability.
The record
- CVE
- CVE-2020-11014
- Published
- Apr 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Simple Ledger
- Product
- Electron Cash SLP Edition
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.6.2
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
No sourced classifications are available.
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