Skip to main content
Mallory
HighVulnerability

CVE-2018-11687: ownerUnderflow

Published Aug 15, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3
EPSS1.4%73rd percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Bitcoin Red Project
IdentifiersCVE-2018-11687CWE-190 · Integer Overflow or Wraparound

CVE-2018-11687 is an integer overflow vulnerability in the distributeBTR function of the Bitcoin Red (BTCR) smart contract, an Ethereum ERC20 token implementation. The contract owner can trigger the flaw by supplying a large address[] array, causing an unauthorized increase in digital assets. Also known as ownerUnderflow, the vulnerability was exploited in the wild in May 2018.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation permits the contract owner to cause an unauthorized increase in digital assets, compromising the integrity of the token contract's asset accounting.

Mitigation

If you can’t patch tonight, do this now.

If immediate code remediation is not possible, disable or stop using the vulnerable batch distribution functionality, especially owner-driven bulk transfers with large address arrays. Restrict owner operations, monitor for anomalous token issuance or balance changes, and alert exchanges and users to the risk. Where possible, pause the contract or otherwise prevent invocation of distributeBTR until a fixed contract is deployed.

Remediation

Patch, then assume compromise.

Remediate by correcting the arithmetic in distributeBTR so that batch distribution calculations cannot overflow or underflow. Use checked arithmetic for all balance and supply operations, validate the maximum permitted size of the address[] input, and ensure that aggregate transfer amounts are bounded before state updates occur. If the contract is upgradeable, deploy a fixed implementation and migrate users to it; if not, replace the vulnerable contract and coordinate exchange and holder migration as appropriate.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Bitcoin Red ProjectBitcoin Redapplication
FAQ

Frequently asked questions

Is CVE-2018-11687 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2018-11687?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2018-11687.
Is there a patch for CVE-2018-11687?
Remediate by correcting the arithmetic in distributeBTR so that batch distribution calculations cannot overflow or underflow. Use checked arithmetic for all balance and supply operations, validate the maximum permitted size of the address[] input, and ensure that aggregate transfer amounts are bounded before state updates occur.
What products are affected by CVE-2018-11687?
Bitcoin Red Project Bitcoin Red.
How severe is CVE-2018-11687?
CVE-2018-11687 has a CVSS v3 score of 7.5 (High) and an EPSS score of 1.4% (73rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.