Excess token minting via manipulated liquidity reserves
Published Jan 3, 2021 · Updated Aug 3, 2024
Incorrect calculation in Stable Yield Credit yCREDIT allows remote attackers to mint excess tokens through the Ethereum contract. The _deposit function values the full WBTC deposit through Chainlink but derives the WBTC added to liquidity from attacker-skewed pool reserves, while minting yCREDIT against the larger value. Exploitation requires attackers to manipulate the WBTC-yCREDIT reserve ratio before depositing, after which the excess tokens can be sold for profit.
Summary
What happened
Incorrect calculation in Stable Yield Credit yCREDIT allows remote attackers to mint excess tokens through the Ethereum contract. The _deposit function values the full WBTC deposit through Chainlink but derives the WBTC added to liquidity from attacker-skewed pool reserves, while minting yCREDIT against the larger value. Exploitation requires attackers to manipulate the WBTC-yCREDIT reserve ratio before depositing, after which the excess tokens can be sold for profit.
The record
- CVE
- CVE-2021-3004
- Published
- Jan 3, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-682
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 1, 2021Exploitation reportedBlockSec-confirmed yCREDIT exploitation
- Jan 3, 2021CVE 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.
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
- BlockSec yCREDIT attack transaction walkthroughfunctional · observed in use
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- BlockSec-confirmed yCREDIT exploitationreported exploitation
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