LiveActive security incident?Get immediate response
CVE Record

CVE-2018-14089: An issue was discovered in a smart contract implementation for Virgo_ZodiacToken, an Ethereum token.

An issue was discovered in a smart contract implementation for Virgo_ZodiacToken, an Ethereum token. In this contract, 'bool sufficientAllowance = allowance <= _value' will cause an arbitrary transfer in the function transferFrom because '<=' is used instead of '>=' (which was intended). An attacker can transfer from any address to his address, and does not need to meet the 'allowance > value' condition.

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

Security readout for executives and security teams

Plain-English summary

Virgo_ZodiacToken reportedly contains a smart contract logic error that can let an attacker move tokens from other addresses without satisfying the intended allowance check. Business impact depends on whether the organization holds, supports, lists, or integrates with this specific Ethereum token contract.

Executive priority

Treat as high priority only if your organization has value, customers, or workflows tied to Virgo_ZodiacToken. The flaw can affect token integrity directly, but the sources do not show broad enterprise exposure or active exploitation.

Technical view

The reported flaw is in transferFrom: the allowance comparison uses allowance <= _value instead of the intended allowance >= _value. That reverses the authorization condition and can permit arbitrary token transfers. The sources do not provide CVSS, fixed versions, CPEs, or confirmed deployment details.

Likely exposure

Exposure appears limited to systems or wallets interacting with Virgo_ZodiacToken, not Ethereum broadly. Relevant exposure includes holders, exchanges, custodians, token-listing services, accounting systems, or smart-contract integrations that trust balances or transfers from this contract.

Exploitation context

The provided sources say an attacker can transfer from any address to their address because the allowance condition is wrong. The CVE is not listed as KEV in the bundle, and no provided source confirms active exploitation.

Researcher notes

The key evidence is the incorrect comparison in transferFrom. Scope is under-specified: vendor, product, versions, CPEs, CVSS, and fix data are absent in the bundle. Validation should focus on contract identity, deployed code, organizational holdings, and transaction anomalies.

Mitigation direction

  • Identify whether your organization holds, lists, or integrates with Virgo_ZodiacToken.
  • Check the token project or vendor guidance for replacement, migration, or deprecation instructions.
  • Temporarily limit deposits, trading, custody actions, or automation tied to the affected token.
  • Reconcile balances and records before relying on affected-token accounting data.
  • Avoid inventing a contract fix; follow authoritative project guidance.

Validation and detection

  • Inventory wallets, services, exchanges, and custody workflows for Virgo_ZodiacToken exposure.
  • Review the deployed contract source or verified code for the vulnerable allowance comparison.
  • Check transaction history for unexpected transferFrom movements affecting owned addresses.
  • Confirm whether any token migration, swap, or deprecation notice exists from the project.
  • Document whether business systems trust balances from the affected contract.
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-14089 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.