LiveActive security incident?Get immediate response
CVE Record

CVE-2020-17752: Integer overflow vulnerability in payable function of a smart contract implementation for an Ethereum token...

Integer overflow vulnerability in payable function of a smart contract implementation for an Ethereum token, as demonstrated by the smart contract implemented at address 0xB49E984A83d7A638E7F2889fc8328952BA951AbE, an implementation for MillionCoin (MON).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-17752 concerns an integer overflow in a payable Ethereum smart contract function for a token implementation identified as MillionCoin (MON). The public record is sparse, with no CVSS score, vendor, patch, or broad product family named. Business urgency depends on whether the organization holds, processes, lists, or integrates this specific token or contract.

Executive priority

Prioritize as a targeted exposure review, not a broad enterprise emergency, unless your organization handles MON or the cited contract. Escalate if customer funds, treasury assets, exchange listings, or automated payment logic depend on it.

Technical view

The CVE describes an integer overflow in a payable function of a smart contract implementation, demonstrated at Ethereum address 0xB49E984A83d7A638E7F2889fc8328952BA951AbE. The source bundle does not provide CWE mapping, vulnerable code details, fixed versions, or generalized affected products beyond the cited contract/token context.

Likely exposure

Exposure appears limited to parties interacting with, holding, integrating, listing, or depending on the cited MillionCoin (MON) smart contract. The CVE data lists vendor and product as n/a, so broader ecosystem impact cannot be inferred from the provided sources.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not state active exploitation. The Etherscan address and reference material support that a vulnerable contract was demonstrated publicly, but they do not establish ongoing attacker activity.

Researcher notes

The public CVE entry is minimal. It identifies the vulnerability class and example contract address but omits root-cause detail, vulnerable source lines, fixed implementation, severity score, affected CPEs, and exploitation evidence. Avoid extrapolating impact beyond the cited token contract without additional evidence.

Mitigation direction

  • Inventory holdings, integrations, listings, and payment flows involving MillionCoin (MON).
  • Avoid new dependency on the cited contract until project guidance is reviewed.
  • Check the token project or contract owner for migration or remediation guidance.
  • Assess user, treasury, and exchange exposure tied to the cited address.
  • Document any accepted residual risk for immutable on-chain exposure.

Validation and detection

  • Confirm whether systems reference address 0xB49E984A83d7A638E7F2889fc8328952BA951AbE.
  • Review wallet, custody, treasury, and exchange records for MON exposure.
  • Check smart contract allowlists, token lists, and payment integrations for the cited contract.
  • Use Etherscan to verify current contract metadata and transaction relevance.
  • Record that no CVSS, fixed version, or vendor advisory was provided.
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-2020-17752 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.