dbcve.org
AtlantApplication

CVE-2018-11429

HIGH · 7.5 CVSS v3.0 Published 2018-07-04
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
ATLANT (ATL) is a smart contract running on Ethereum. The mint function has an integer overflow that allows minted tokens to be arbitrarily retrieved by the contract owner.

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 ATLANT (ATL) Ethereum smart contract contains an integer overflow vulnerability in its mint function that allows the contract owner to arbitrarily retrieve minted tokens. This is a classic integer overflow bug where arithmetic operations exceed the maximum value an integer can store, enabling unauthorized token manipulation.

MitigationFix the integer overflow in the mint function using SafeMath library or compiler-based overflow checks, and consider upgrading to a newer Solidity version with built-in overflow protections. If the contract is not upgradeable, a migration to a patched contract may be necessary.

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
AtlantApplication
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 the ATLANT token contract
    Locate the contract address for the ATLANT (ATL) token you interact with. Cross-reference the token name, symbol (ATL), and contract address against official ATLANT sources or block explorers such as Etherscan.
    Affected if The contract address matches the ATLANT token and the token symbol is ATL.
  2. Obtain the contract source code
    On Etherscan or a similar block explorer, navigate to the Contract tab for the ATLANT token contract and verify that the source code is available. If the contract is verified, you will see the Solidity source; if not, you only have the bytecode which limits analysis.
    Affected if Source code is verified and available for inspection.
  3. Locate the mint function
    Search the source code for the 'mint' function definition. Identify its parameter types and the arithmetic operations performed within the function, particularly any addition or multiplication operations on token supply or balances.
    Affected if A mint function exists in the contract that performs arithmetic on token amounts.
  4. Check for SafeMath usage
    Examine whether the contract imports and uses the SafeMath library for arithmetic operations, particularly within the mint function. Look for 'using SafeMath for' declarations and '.add()' or '.mul()' method calls instead of native '+' or '*' operators.
    Affected if SafeMath is NOT used for arithmetic operations in the mint function, or the function uses native operators without overflow checks.
  5. Determine if the contract is upgradeable
    Check for upgradeability patterns in the contract code: look for 'Ownable', 'Upgradeable', 'Proxy', or upgradeability-related function signatures. Also check the contract creation transaction to see if it deploys a proxy pattern.
    Affected if The contract is not upgradeable, meaning the vulnerable code cannot be replaced without migrating to a new contract address.

You are affected if you hold or interact with the ATLANT (ATL) token and the contract's mint function lacks SafeMath or compiler-based overflow protection, especially if the contract is not upgradeable.

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

Fix the integer overflow in the mint function using SafeMath library or compiler-based overflow checks, and consider upgrading to a newer Solidity version with built-in overflow protections. If the contract is not upgradeable, a migration to a patched contract may be necessary.

Fix this in Atlant 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-11429 — 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-11429 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