LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13085: The mintToken function of a smart contract implementation for FreeCoin (FREE), an Ethereum token, has an in...

The mintToken function of a smart contract implementation for FreeCoin (FREE), an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.

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

Security readout for executives and security teams

Plain-English summary

This CVE concerns a FreeCoin (FREE) Ethereum token contract. Its minting function can overflow, allowing the contract owner to set any user's token balance to any value. Business impact depends on whether the organization holds, accepts, or depends on this specific token contract.

Executive priority

Treat this as targeted exposure, not a broad infrastructure emergency. Prioritize review if the business relies on FREE token balances, accepts the token, or operates related smart-contract infrastructure.

Technical view

The CVE describes an integer overflow in the FreeCoin smart contract mintToken function. The reported impact is owner-controlled arbitrary balance assignment for any user. The public bundle provides no CVSS, CWE, affected CPEs, patch version, or confirmed affected deployment list.

Likely exposure

Exposure appears limited to deployments or integrations of the referenced FreeCoin (FREE) Ethereum token contract. The CVE lists vendor, product, and versions as n/a, so do not generalize this finding to other Ethereum tokens without contract-level confirmation.

Exploitation context

The source bundle does not indicate active exploitation, and KEV is false. The described capability requires the contract owner role, so practical risk centers on owner trust, owner key compromise, or use of a vulnerable implementation in production.

Researcher notes

Key gaps are affected contract address scope, exploit evidence, patch status, and severity scoring. The owner-only condition is central to triage, but the CVE still represents a serious token-integrity failure where the vulnerable contract is trusted.

Mitigation direction

  • Check whether your organization holds, accepts, or integrates the referenced FreeCoin token.
  • Consult FreeCoin or maintainer guidance before trusting balances from the affected contract.
  • Avoid deploying the referenced implementation in new contracts or integrations.
  • If operating a related contract, migrate only after reviewed overflow-safe mint logic is available.

Validation and detection

  • Identify the exact token contract addresses used by your systems or wallets.
  • Confirm whether those contracts use the referenced FreeCoin mintToken implementation.
  • Review whether any business workflow trusts FREE balances for value, access, or accounting.
  • Check historical balance anomalies through trusted blockchain analytics or internal records.
Prepared
Confidence
medium
Sources
3

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-13085 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
2Source 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.