Permanent fund loss via unchecked bet parameters
Published Sep 11, 2023 · Updated Sep 26, 2024
Incorrect calculation in an Ethereum casino smart contract allows remote attackers to cause permanent participant fund loss. The public betOnNumber function derives betSize from msg.value, insufficiently validates monetary parameters, and updates casino.balance without checking whether send() succeeded. Any blockchain participant can call the function, but the published record identifies neither the deployed contract address nor a canonical product.
Summary
What happened
Incorrect calculation in an Ethereum casino smart contract allows remote attackers to cause permanent participant fund loss. The public betOnNumber function derives betSize from msg.value, insufficiently validates monetary parameters, and updates casino.balance without checking whether send() succeeded. Any blockchain participant can call the function, but the published record identifies neither the deployed contract address nor a canonical product.
The record
- CVE
- CVE-2023-36980
- Published
- Sep 11, 2023
- Updated
- Sep 26, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-682, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 11, 2023CVE publishedPublication date reported by the CVE source.
- Sep 26, 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.
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