CVE-2018-13210
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 · uneditedThe sell function of a smart contract implementation for Providence Crypto Casino (PVE) (Contract Name: ProvidenceCasinoToken), an Ethereum token, has an integer overflow in which "amount * sellPrice" can be zero, consequently reducing a seller's assets.
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 · high confidenceThe sell function in the ProvidenceCasinoToken smart contract contains an integer overflow vulnerability where the calculation 'amount * sellPrice' can result in zero due to arithmetic overflow. This allows attackers or triggers the condition to cause sellers to transfer their tokens to the contract without receiving the corresponding ETH payment, effectively draining user assets.
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 dataall versionsCVSS 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
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if you are using ProvidenceCasinoTokenCheck your deployed contract's name or address by querying the blockchain explorer or your internal records for contracts named 'ProvidenceCasinoToken' or 'Providence Crypto Casino'Affected if Your environment uses this specific smart contract
-
Locate the sell function in your deployed contractView the source code or decompiled bytecode of your ProvidenceCasinoToken contract and search for a function named 'sell' or 'sellToken' that accepts an 'amount' parameterAffected if A sell function exists in your deployed contract
-
Verify vulnerable arithmetic without SafeMath protectionInspect the sell function for the calculation 'amount * sellPrice' and confirm it uses standard Solidity arithmetic operators (*, +, -, /) instead of SafeMath library functions (add, sub, mul, div)Affected if The contract uses direct arithmetic operators like '*' for the amount*sellPrice calculation without SafeMath protection
-
Confirm the overflow condition is exploitableCheck if sellPrice is a public state variable that can be set to a value large enough (e.g., values approaching 2^256) to cause amount*sellPrice to overflow to zeroAffected if sellPrice is externally settable or can be manipulated to trigger overflow in the multiplication
-
Check contract version and compilation settingsDetermine the Solidity version used to compile the contract - versions prior to 0.8.0 do not have built-in overflow checks and are vulnerable when not using SafeMathAffected if The contract was compiled with Solidity 0.8.0 or later without explicit unchecked blocks, or with versions below 0.8.0 using direct arithmetic
Your environment is affected if you are running a ProvidenceCasinoToken contract where the sell function performs 'amount * sellPrice' without SafeMath protection, allowing the multiplication to overflow and result in zero ETH payment while tokens are transferred.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace vulnerable arithmetic operations with SafeMath library functions that detect and prevent integer overflows, then redeploy the fixed contract and migrate any stuck user funds.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13210 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-13210 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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