dbcve.org
SmartpaymentApplication · Smartpayment Project

CVE-2018-13523

HIGH · 7.5 CVSS v3.0 Published 2018-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The mintToken function of a smart contract implementation for SmartPayment, 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 confidence

The SmartPayment Ethereum token contract's mintToken function contains an integer overflow vulnerability that allows the contract owner to manipulate any user's token balance to arbitrary values. This is a critical access control and data integrity flaw combined with arithmetic overflow.

MitigationThe contract must be upgraded to use SafeMath libraries or Solidity 0.8+ with built-in overflow checks, and proper access controls should be implemented to restrict balance modifications. Token holders should be notified of the vulnerability and potential need for token migration.

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
SmartpaymentApplication
Affected:all versions

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
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 checks

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

  1. Identify if you have interacted with the SmartPayment token contract
    Review your Ethereum wallet transaction history or token holdings for the SmartPayment token contract address. If you hold or have transacted with this specific token, you may be affected.
    Affected if You hold SmartPayment tokens or have a transaction history with the SmartPayment token contract.
  2. Locate and inspect the deployed contract source code
    Search for the SmartPayment token contract on Etherscan or similar block explorers using the contract address. Obtain the Solidity source code and locate the mintToken function.
    Affected if The contract source code contains a mintToken function with arithmetic operations on token balances without SafeMath.
  3. Verify SafeMath library usage
    Search the contract source code for 'using SafeMath' statements or library imports. Check whether arithmetic operations (+, -, *, /) in mintToken use SafeMath methods (.add, .sub, .mul, .div).
    Affected if The contract does not import or use SafeMath library for arithmetic operations in mintToken.
  4. Check Solidity compiler version
    Locate the 'pragma solidity' directive in the contract source code. Identify the compiler version number specified.
    Affected if The contract uses Solidity version below 0.8.x (which has built-in overflow checks).
  5. Inspect mintToken function access controls
    Review the mintToken function declaration for visibility modifiers (public, external, internal, private) and any require statements or access control modifiers. Check if the function has any restrictions on who can call it.
    Affected if The mintToken function is declared as public or external without proper access control restrictions, allowing the contract owner to manipulate any user's balance.

You are affected if you hold or have transacted with the SmartPayment token contract, especially if the deployed contract lacks SafeMath usage or uses Solidity below 0.8 and has an unprotected mintToken function that allows arbitrary balance modifications.

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

The contract must be upgraded to use SafeMath libraries or Solidity 0.8+ with built-in overflow checks, and proper access controls should be implemented to restrict balance modifications. Token holders should be notified of the vulnerability and potential need for token migration.

Fix this in Smartpayment Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-13523 — 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-2018-13523 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