dbcve.org
PandoraApplication · Pandora Project

CVE-2018-13144

HIGH · 7.5 CVSS v3.1 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
The transfer and transferFrom functions of a smart contract implementation for Pandora (PDX), an Ethereum token, have an integer overflow. NOTE: this has been disputed by a third party.

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

Integer overflow vulnerability in the transfer() and transferFrom() functions of the Pandora (PDX) Ethereum token smart contract. The vulnerability allows arithmetic operations on token balances to exceed maximum integer limits, potentially enabling attackers to manipulate transfer amounts or balances. This is a classic Solidity vulnerability common in contracts using Solidity versions prior to 0.8 that lack built-in overflow protection.

MitigationDeploy a patched contract version using SafeMath library (Solidity < 0.8) or compiled with Solidity 0.8+ (which includes built-in overflow checks). Coordinate token migration for existing holders to the new secure contract. NOTE: Third party dispute may warrant independent verification of the vulnerability claim.

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
PandoraApplication
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.1/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. Confirm PDX token holdings or interaction
    Check your Ethereum wallet, exchange account, or smart contract interaction history for Pandora (PDX) token balances or transactions
    Affected if You hold PDX tokens or have interacted with the Pandora token contract on any Ethereum-compatible blockchain
  2. Identify the PDX contract address
    Locate the contract address used for your PDX tokens - check Etherscan or your wallet's token transfer records for the 'to' address in PDX transactions
    Affected if You are using a contract address that corresponds to the vulnerable Pandora token deployment
  3. Retrieve the contract source code
    On Etherscan (or similar block explorer), go to the Contract tab for the PDX token address and look for verified source code. If source is not verified, the contract bytecode will be available
    Affected if The contract source code is available and shows Solidity version prior to 0.8 without SafeMath library imported
  4. Check Solidity compiler version
    In the contract source code metadata or verified source tab, locate the 'pragma solidity' declaration at the top of the contract file
    Affected if The contract declares a Solidity version below 0.8 (e.g., pragma solidity ^0.4.0 or ^0.6.0)
  5. Verify overflow protection in transfer functions
    Locate the transfer() and transferFrom() function definitions in the contract source code. Check whether they use SafeMath methods (like safeAdd, safeSub, safeMul) or direct arithmetic operators (+, -, *)
    Affected if The transfer or transferFrom functions use direct arithmetic (balance[from] + amount, etc.) without SafeMath library calls or Solidity 0.8+ overflow checks

You are affected if you hold or interact with Pandora (PDX) tokens deployed from a Solidity version below 0.8 where the transfer() and transferFrom() functions perform arithmetic without SafeMath or built-in overflow protection.

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 patched contract version using SafeMath library (Solidity < 0.8) or compiled with Solidity 0.8+ (which includes built-in overflow checks). Coordinate token migration for existing holders to the new secure contract. NOTE: Third party dispute may warrant independent verification of the vulnerability claim.

Fix this in Pandora 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-13144 — 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-13144 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