LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10376: An integer overflow in the transferProxy function of a smart contract implementation for SmartMesh (aka SMT...

An integer overflow in the transferProxy function of a smart contract implementation for SmartMesh (aka SMT), an Ethereum ERC20 token, allows attackers to accomplish an unauthorized increase of digital assets via crafted _fee and _value parameters, as exploited in the wild in April 2018, aka the "proxyOverflow" 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-10376 is a SmartMesh SMT token smart-contract flaw that could let attackers inflate digital assets through an integer overflow. The source bundle states it was exploited in April 2018. Business risk is concentrated where organizations hold, list, custody, or programmatically interact with the affected SMT ERC20 contract.

Executive priority

Treat as high priority only if the organization had SMT exposure or supports legacy ERC20 assets. The main concern is financial integrity, accounting accuracy, and customer impact from historical or unresolved token inflation.

Technical view

The issue is an integer overflow in the SmartMesh ERC20 transferProxy function. Crafted _fee and _value parameters could produce unauthorized asset increases. The bundle does not provide CVSS, CPEs, specific fixed versions, or a confirmed patch reference, so remediation should be tied to SmartMesh or exchange guidance.

Likely exposure

Exposure is most likely for exchanges, custodians, wallets, DeFi tooling, or internal systems that handled the affected SmartMesh SMT ERC20 contract. General Ethereum exposure is not implied by the bundle.

Exploitation context

The CVE description says exploitation occurred in the wild in April 2018 under the proxyOverflow name. KEV is false, and the bundle does not provide current active-exploitation evidence.

Researcher notes

Evidence is specific to SmartMesh SMT and the proxyOverflow integer-overflow class. The source bundle lacks CPEs, CVSS, fixed versions, and detailed vendor remediation. Avoid broad claims beyond SMT without independent contract review.

Mitigation direction

  • Check SmartMesh and exchange advisories for confirmed migration or contract guidance.
  • Avoid relying on vulnerable SMT contract balances until exposure is validated.
  • Reconcile historical SMT balances against trusted transaction records.
  • For owned contracts, use checked arithmetic and reviewed ERC20 libraries.
  • Document any token-listing, custody, or accounting compensating controls.

Validation and detection

  • Inventory systems that held, listed, custodied, or indexed SMT.
  • Identify the exact SMT contract addresses historically supported.
  • Review transferProxy implementation for unchecked arithmetic involving _fee and _value.
  • Look for abnormal balance increases around the April 2018 incident period.
  • Confirm whether any migration or replacement contract was adopted.
Prepared
Confidence
medium
Sources
5

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-10376 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
4Source 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.