dbcve.org
Node TokenApplication · Intchain

CVE-2018-12080

HIGH · 7.5 CVSS v3.0 Published 2018-06-25
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 Internet Node Token (INT), a tradable Ethereum ERC20 token, has no period constraint, which allows the owner to increase the total supply of the digital assets arbitrarily so as to make profits, aka the "tradeTrap" issue.

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 Internet Node Token (INT) ERC20 smart contract lacks any time-based or quantitative constraints, allowing the contract owner to mint unlimited new tokens at any time. This enables the owner to artificially inflate the total supply and potentially profit through trading, constituting a privileged abuse vulnerability known as 'tradeTrap'.

MitigationDeploy a fixed version of the contract with proper minting controls (e.g., caps, time locks, multi-sig requirements) and migrate all token holdings and balances to the new contract; ensure future token audits include minting authorization checks.

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
Node 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 hold Intchain Node Token (INT)
    Check your cryptocurrency wallet or exchange balance for INT tokens. If you do not hold INT tokens, you are not directly affected as a holder.
    Affected if You hold Intchain Node Token (INT) in any wallet or exchange
  2. Locate the deployed INT smart contract address
    Check your transaction history or token audit documentation for the contract address of the Intchain Node Token you hold.
    Affected if You cannot locate a contract address - verify you have the correct token
  3. Verify if mintToken function exists in the contract
    Using a blockchain explorer (such as Etherscan for Ethereum-based tokens), view the contract source code or ABI. Search for a function named 'mintToken' or 'mint'. If this function exists, the vulnerability may be present.
    Affected if The contract source code contains a mintToken or mint function accessible to the owner
  4. Check for minting constraints in the contract code
    If mintToken exists, examine its implementation. Look for any require statements, time-based locks, caps, or multi-sig requirements that would restrict unlimited minting. The vulnerability exists if no such constraints are present.
    Affected if The mintToken function has no require statements, caps, time locks, or quantitative restrictions on token creation
  5. Review total supply for anomalies
    Check the current totalSupply of INT on a blockchain explorer. Compare against historical data or expected supply. Unlimited minting would allow the owner to arbitrarily increase the total supply without limit.
    Affected if Total supply has increased unexpectedly or can be increased arbitrarily by the contract owner

If you hold INT tokens and the deployed contract contains an unbounded mintToken function accessible to the owner, you are affected by this vulnerability.

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

Deploy a fixed version of the contract with proper minting controls (e.g., caps, time locks, multi-sig requirements) and migrate all token holdings and balances to the new contract; ensure future token audits include minting authorization checks.

Fix this in Node Token Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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