dbcve.org
MavcashApplication · Mavcash Project

CVE-2018-13614

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 MAVCash, 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 MAVCash Ethereum token smart contract's mintToken function contains an integer overflow vulnerability. This allows the contract owner to manipulate any user's token balance to arbitrary values by exploiting the overflow condition when minting tokens.

MitigationReplace the mintToken function with a SafeMath-based implementation to prevent integer overflow, or upgrade to a standard ERC-20 token contract from a audited library like OpenZeppelin. Consider redeploying the contract with proper access controls if tokens have not yet been distributed.

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
MavcashApplication
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 deployed the MAVCash token contract
    Search your deployment records or blockchain explorers for contracts named 'MAVCash' or 'MAVToken' that you own or control. Note the contract address.
    Affected if You have deployed a MAVCash token contract and are the contract owner (or the owner address is compromised).
  2. Check if you are the contract owner
    Using a blockchain explorer or web3 call, query the owner role of the deployed contract. Common methods include calling 'owner()' or checking the contract's OpenZeppelin AccessControl roles.
    Affected if The calling address matches the contract owner role, meaning you have the ability to call the vulnerable mintToken function.
  3. Locate and inspect the mintToken function source code
    If the contract is verified on Etherscan or similar explorer, view the Solidity source code. Search for the 'mintToken' function and examine its implementation for arithmetic operations on token balances.
    Affected if The mintToken function performs addition on balances without using SafeMath or OpenZeppelin's SafeERC20 libraries, allowing integer overflow.
  4. Verify lack of overflow protection in balance updates
    Examine the lines in mintToken that update user balances (e.g., 'balances[target] = balances[target] + amount'). Confirm there is no 'require' or 'assert' checking for overflow before the addition.
    Affected if The code directly performs 'balance + amount' without overflow checks, making the integer overflow exploitable.
  5. Confirm mintToken can be called by the owner
    Check the function modifier on mintToken (e.g., 'onlyOwner' or 'require(msg.sender == owner)'). Verify the function is callable without additional constraints like time locks or multi-sig requirements.
    Affected if The owner can directly call mintToken without multiparty authorization, allowing arbitrary balance manipulation.

You are affected if you have deployed the MAVCash token contract and the mintToken function performs balance arithmetic without SafeMath overflow protection, allowing the owner to arbitrarily manipulate token balances.

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

Replace the mintToken function with a SafeMath-based implementation to prevent integer overflow, or upgrade to a standard ERC-20 token contract from a audited library like OpenZeppelin. Consider redeploying the contract with proper access controls if tokens have not yet been distributed.

Fix this in Mavcash 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-2018-13614 — 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-13614 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