dbcve.org
Digital Cloud TokenApplication · Digital Cloud Token Project

CVE-2018-13519

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 mint function of a smart contract implementation for DigitalCloudToken, 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 · moderate confidence

The DigitalCloudToken smart contract's mint function contains an integer overflow vulnerability that permits the contract owner to arbitrarily set any user's token balance. This occurs due to unchecked arithmetic operations when minting new tokens, potentially allowing the owner to inflate balances beyond normal constraints.

MitigationImplement SafeMath library or explicit overflow/underflow checks in the mint function, and consider adding additional access controls such as multi-signature requirements for privileged operations.

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
Digital Cloud TokenApplication
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 DigitalCloudToken smart contract
    Search your smart contract deployment records, blockchain explorers, or contract registries for contracts named 'DigitalCloudToken' or 'DCT'. Review any contract artifacts or deployment configurations in your project.
    Affected if A DigitalCloudToken contract instance is deployed on any blockchain network you operate or monitor.
  2. Locate and inspect the mint function source code
    Obtain the contract source code from Etherscan, your repository, or by decompiling the deployed bytecode using a tool like Remix or Panoramix. Search for a function named 'mint' in the source.
    Affected if The mint function exists and performs arithmetic operations on token balances without SafeMath library or explicit overflow/underflow checks.
  3. Check for SafeMath library usage in the contract
    Search the contract source code for 'using SafeMath' statement or SafeMath library imports. Also check if arithmetic operations use .add(), .sub(), .mul() methods instead of +, -, * operators.
    Affected if SafeMath is not imported, not used, or arithmetic operations use unchecked operators (+, -, *) instead of SafeMath methods.
  4. Verify access control on the mint function
    Examine the mint function declaration for access modifiers like 'onlyOwner', 'onlyAdmin', or role-based access control (RBAC). Check if any address can call the function or if there are missing ownership checks.
    Affected if The mint function lacks proper access control modifiers, allowing unauthorized balance manipulation.
  5. Check current token supply and balance state
    Call the totalSupply() function on the deployed contract. Query balances of accounts using balanceOf(). Compare against expected supply or look for unusually large balances indicating potential exploitation.
    Affected if totalSupply() returns a value exceeding reasonable token emission caps or specific accounts hold balances inconsistent with normal minting operations.

You are affected if you have deployed the DigitalCloudToken contract and its mint function lacks SafeMath or overflow checks, allowing unchecked arithmetic that could permit arbitrary balance manipulation.

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

Implement SafeMath library or explicit overflow/underflow checks in the mint function, and consider adding additional access controls such as multi-signature requirements for privileged operations.

Fix this in Digital Cloud Token Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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