YasudemApplication · Yasudem Project

CVE-2018-13584

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 yasudem, 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 mintToken function in the yasudem Ethereum smart contract contains an integer overflow vulnerability that permits the contract owner to set any user's token balance to an arbitrary value, bypassing proper input validation and creating a critical integrity issue.

MitigationReplace unsafe arithmetic operations with SafeMath library functions to prevent integer overflows, and implement proper access controls to restrict balance manipulation capabilities.

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
YasudemApplication
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. Locate the yasudem smart contract
    Search your deployed contracts or check block explorers for any contract named Yasudem or YSD (token symbol). Obtain the contract source code or ABI if verified on Etherscan or similar explorer.
    Affected if A contract matching Yasudem is deployed in your environment
  2. Identify the mintToken function
    Within the contract source code, locate the function named mintToken. This is typically a public or external function that accepts parameters for target address and token amount.
    Affected if The mintToken function exists in the deployed contract
  3. Inspect arithmetic operations in mintToken
    Examine all arithmetic operations (addition, multiplication, subtraction) within the mintToken function body. Look for direct usage of Solidity operators (+, -, *) without SafeMath library wrappers.
    Affected if The mintToken function contains direct arithmetic on token balances without using SafeMath methods (such as add, sub, mul)
  4. Verify contract ownership model
    Check if the contract implements an owner variable and uses a modifier (commonly named onlyOwner) to restrict access to mintToken. Review who holds the owner role in your deployment.
    Affected if The contract has an owner role that can call mintToken and there is no additional oversight or multi-signature requirement
  5. Compare to vulnerable pattern
    The vulnerable pattern is: balanceOf[target] = balanceOf[target] + tokenAmount (or similar) where the addition can overflow if balanceOf[target] is close to the maximum uint256 value. Confirm whether your contract exhibits this exact pattern.
    Affected if The mintToken function directly adds to a user's balance using unsafe arithmetic that can overflow

Your environment is affected if the Yasudem contract is deployed and its mintToken function uses direct arithmetic operators instead of SafeMath library functions for 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

Replace unsafe arithmetic operations with SafeMath library functions to prevent integer overflows, and implement proper access controls to restrict balance manipulation capabilities.

Fix this in Yasudem Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-13584 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