LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10299: An integer overflow in the batchTransfer function of a smart contract implementation for Beauty Ecosystem C...

An integer overflow in the batchTransfer function of a smart contract implementation for Beauty Ecosystem Coin (BEC), the Ethereum ERC20 token used in the Beauty Chain economic system, allows attackers to accomplish an unauthorized increase of digital assets by providing two _receivers arguments in conjunction with a large _value argument, as exploited in the wild in April 2018, aka the "batchOverflow" issue.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-10299 is a smart-contract flaw in Beauty Ecosystem Coin that allowed unauthorized creation of digital assets. The public record says it was exploited in April 2018. Business impact is concentrated where BEC was held, traded, custodied, or integrated, especially exchanges and wallets relying on the token balance state.

Executive priority

Prioritize immediately if the organization handled BEC or relied on affected token balances. For most enterprises without BEC exposure, urgency is low, but the case is a strong control lesson for digital-asset listing and custody reviews.

Technical view

The issue is an integer overflow in the BEC ERC20 token contract's batchTransfer function. Crafted transfer parameters could make arithmetic wrap and inflate balances. Sources identify this as the batchOverflow issue. The CVE record does not provide CVSS, CWE, CPEs, version ranges, or a named vendor patch.

Likely exposure

Direct exposure appears limited to Beauty Ecosystem Coin and systems that accepted, traded, custodied, indexed, or settled BEC balances. Secondary exposure may exist in copied smart-contract code with similar batchTransfer arithmetic. The source bundle does not identify affected conventional software products or enterprise platforms.

Exploitation context

The CVE description states exploitation occurred in the wild in April 2018. Public references include exchange suspension notices and security writeups. There is no KEV listing in the provided bundle, and no evidence here of ongoing exploitation beyond the historical incident.

Researcher notes

Evidence is strong for the BEC batchOverflow class and historical exploitation, but incomplete for formal scoring and affected-version metadata. Avoid generalizing this CVE to all ERC20 tokens; validate specific contract code and operational dependencies. No source in the bundle names a universal patch.

Mitigation direction

  • Check BeautyChain, exchange, and wallet guidance before resuming affected BEC operations.
  • Suspend or restrict BEC deposits, withdrawals, and trading until exposure is understood.
  • Review related token contracts for overflow-safe arithmetic in batch transfer logic.
  • Treat unsupported vulnerable contracts as requiring project-level remediation or replacement.
  • Add smart-contract security review gates before listing or integrating tokens.

Validation and detection

  • Inventory any BEC holdings, custody, trading, settlement, or indexing integrations.
  • Confirm whether integrated token contracts match the vulnerable BEC implementation.
  • Review historical balance and transfer records for abnormal supply or balance inflation.
  • Verify exchange and project actions against cited suspension and security notices.
  • Document whether cloned contract code uses checked arithmetic or equivalent safeguards.
Prepared
Confidence
medium
Sources
8

Public sources used

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-10299 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
7Source links

CVSS and timeline data

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

Source materials

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.