dbcve.org
BlockchainApplication · Ethereum

CVE-2023-36980

MEDIUM · 5.3 CVSS v3.1 Published 2023-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue in Ethereum Blockchain v0.1.1+commit.6ff4cd6 cause the balance to be zeroed out when the value of betsize+casino.balance exceeds the threshold.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

In Ethereum Blockchain v0.1.1+commit.6ff4cd6, a logic vulnerability causes the entire casino balance to be zeroed out when a bet transaction would result in betsize+casino.balance exceeding a threshold. Instead of properly rejecting the bet or enforcing limits, the contract incorrectly wipes the entire balance, leading to potential fund loss.

MitigationFix the threshold check logic to properly reject or limit bets that would exceed the threshold rather than zeroing the balance; implement proper input validation and error handling.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BlockchainApplication
Affected:= 0.1.1\+commit.6ff4cd6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Ethereum Blockchain version
    Run `geth version` or check the git commit hash of your Ethereum node installation to verify it matches 0.1.1+commit.6ff4cd6
    Affected if The installed version is exactly 0.1.1+commit.6ff4cd6
  2. Identify casino contract deployment
    Query your blockchain state or deployment logs to determine if a casino-style smart contract has been deployed on your network
    Affected if A casino contract exists on your blockchain instance
  3. Verify casino balance handling
    Inspect the casino contract source code or bytecode for logic that handles the condition where betsize plus casino balance exceeds a threshold
    Affected if The contract contains threshold comparison logic that could trigger balance zeroing instead of bet rejection
  4. Test threshold behavior
    Simulate a bet transaction where (betsize + casino.balance) would exceed the threshold and observe the resulting casino balance
    Affected if The entire casino balance becomes zero rather than the bet being rejected or limited

You are affected if running Ethereum Blockchain version 0.1.1+commit.6ff4cd6 with a deployed casino contract that exhibits the balance-zeroing behavior when bets exceed the threshold.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix the threshold check logic to properly reject or limit bets that would exceed the threshold rather than zeroing the balance; implement proper input validation and error handling.

Fix this in Blockchain Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36980 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data