LiveActive security incident?Get immediate response
CVE Record

CVE-2018-17882: An Integer overflow vulnerability exists in the batchTransfer function of a smart contract implementation f...

An Integer overflow vulnerability exists in the batchTransfer function of a smart contract implementation for CryptoBotsBattle (CBTB), an Ethereum token. This vulnerability could be used by an attacker to create an arbitrary amount of tokens for any user.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CryptoBotsBattle (CBTB), an Ethereum token, had an integer overflow in its batchTransfer function. The reported impact is economic: an attacker could create arbitrary token amounts for any user, undermining token integrity and trust. No CVSS score, vendor/product metadata, or confirmed active exploitation is provided in the source bundle.

Executive priority

Treat as high priority only if the organization had CBTB exposure. The main concern is token integrity and financial trust, not compromise of general IT infrastructure. If there is no CBTB holding, listing, custody, or integration, business urgency is low.

Technical view

CVE-2018-17882 describes an integer overflow in the CBTB token smart contract batchTransfer implementation. The stated result is arbitrary token creation for any user. The source bundle points to the contract code and a third-party write-up, but does not provide CVSS, CWE mapping, affected versions, or remediation details.

Likely exposure

Exposure appears limited to organizations that held, listed, custodied, integrated, or accepted CryptoBotsBattle CBTB tied to the referenced Ethereum contract. General web, cloud, endpoint, and non-CBTB systems are not indicated as affected by the provided sources.

Exploitation context

The CVE states the flaw could be used to create arbitrary tokens. The source bundle marks KEV as false and provides no cited evidence of active exploitation, exploit prevalence, patched contract migration, or exchange response.

Researcher notes

The record is sparse: affected vendor/product fields are n/a, severity is unknown, and no official fix is named. Analysis should stay tied to CBTB and the referenced contract unless additional evidence identifies other affected implementations.

Mitigation direction

  • Identify any CBTB holdings, listings, custody, payment, or accounting integrations.
  • Check vendor, project, exchange, or custodian guidance before accepting further CBTB activity.
  • Review token exposure limits and suspend unsupported CBTB workflows if risk is unresolved.
  • For smart contract integrations, require overflow-safe arithmetic and independent contract review.

Validation and detection

  • Confirm whether systems reference Ethereum contract 0x4daa9dc438a77bd59e8a43c6d46cbfe84cd04255.
  • Review CBTB balances, listings, and custody records for exposure.
  • Compare internal contract assumptions against the Etherscan source code reference.
  • Check whether any migration, delisting, or remediation notice exists from trusted counterparties.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-17882 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.