CVE-2018-13126
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 · uneditedMoxyOnePresale 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 confidenceThe MoxyOnePresale Ethereum smart contract contains an integer overflow vulnerability in its mint function. This allows the contract owner to manipulate token minting through arithmetic overflow, enabling arbitrary retrieval of minted tokens beyond intended limits.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if you deployed the MoxyOnePresale smart contractLocate your deployed contract by searching your deployment records or blockchain explorers for a contract named 'MoxyOnePresale' or 'MoxyOne Presale'. Verify the contract address matches the MoxyOnePresale deployment.Affected if You have deployed the MoxyOnePresale contract at any address.
-
Check the Solidity compiler version usedRetrieve the contract metadata or source code and identify the Solidity version in the pragma statement (e.g., 'pragma solidity ^0.4.24;').Affected if The contract uses Solidity version below 0.8.0 without explicit overflow checks.
-
Inspect the mint function for SafeMath usageLocate the mint function in the contract source code and verify whether arithmetic operations use the SafeMath library (look for 'using SafeMath for uint256;' and '.add()', '.mul()' methods) or if they use raw arithmetic operators (+, *, etc.).Affected if The mint function uses raw arithmetic operators (+, *, -, /) without SafeMath library or equivalent overflow protection.
-
Verify the mint function is accessible to the ownerCheck the function modifier on the mint function (typically 'onlyOwner' or similar) and confirm the owner account can call this function directly.Affected if The contract owner can directly invoke the mint function without timelock or multi-signature requirements.
If you have deployed the MoxyOnePresale contract and its mint function uses raw arithmetic without SafeMath or Solidity 0.8+ overflow checks, your contract is vulnerable to integer overflow exploitation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement SafeMath library for arithmetic operations or use Solidity 0.8+ built-in overflow checks to prevent integer overflow in token minting operations.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13126 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-13126 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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