CVE-2018-13547
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 mintToken function of a smart contract implementation for Providence Crypto Casino (PVE) (Contract Name: ProvidenceCasinoToken), an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.
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 mintToken function in the ProvidenceCasinoToken smart contract contains an integer overflow vulnerability that allows the contract owner to manipulate arbitrary user token balances to any value. This is a critical access control and arithmetic safety flaw in the Solidity smart contract's token minting logic.
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 ProvidenceCasinoToken contract deploymentSearch your deployed smart contracts for an instance named ProvidenceCasinoToken or a contract with mintToken function that handles token operationsAffected if A contract named ProvidenceCasinoToken is found in your environment
-
Locate the mintToken function in source codeIf you have access to the contract source code, search for a function named 'mintToken' and review its implementationAffected if A mintToken function exists that performs arithmetic operations on token balances without SafeMath
-
Verify SafeMath library usageInspect the contract code to determine if SafeMath library functions (add, sub, mul, div) are used for arithmetic operations in mintToken and balance modificationsAffected if Arithmetic operations in mintToken use direct operators (+, -, *, /) instead of SafeMath library functions
-
Check owner access control on mintTokenReview the mintToken function declaration to see if it includes an access control modifier (such as onlyOwner) restricting who can call itAffected if The mintToken function lacks access control modifiers or allows arbitrary balance manipulation by the owner
-
Inspect balance manipulation logicExamine the mintToken function body to see if it allows setting any user's balance to an arbitrary value without restrictionsAffected if The function permits the contract owner to directly modify user balances to any value
Your environment is affected if you have deployed the ProvidenceCasinoToken contract and the mintToken function uses direct arithmetic operations without SafeMath, allowing the owner to manipulate user balances arbitrarily.
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 manual arithmetic operations with SafeMath library functions to prevent integer overflow/underflow, and implement proper access controls to restrict token minting capabilities to authorized functions only. Consider migrating to a patched contract version if upgradeable.
- 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-13547 — 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-13547 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