LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000203: Soar Labs Soar Coin version up to and including git commit 4a2aa71ee21014e2880a3f7aad11091ed6ad434f (latest...

Soar Labs Soar Coin version up to and including git commit 4a2aa71ee21014e2880a3f7aad11091ed6ad434f (latest release as of Sept 2017) contains an intentional backdoor vulnerability in the function zero_fee_transaction() that can result in theft of Soar Coins by the "onlycentralAccount" (Soar Labs) after payment is processed.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes an intentional backdoor in Soar Labs Soar Coin smart-contract code. The reported effect is direct theft of Soar Coins by the central account controlled by Soar Labs after payment processing. For holders or businesses that accepted Soar Coin, the concern is asset loss and trust failure, not a conventional server compromise.

Executive priority

Treat this as high priority only if the organization held, accepted, or integrated Soar Coin. The main business risk is direct financial loss and counterparty exposure. If there is no Soar Coin dependency, record the CVE as not applicable after validation.

Technical view

The CVE identifies vulnerable Soar Coin code through git commit 4a2aa71ee21014e2880a3f7aad11091ed6ad434f. The named function is zero_fee_transaction(), tied to an onlycentralAccount privilege. Public metadata does not provide CVSS, CWE, CPE, or patched-version details, so validation should focus on code provenance and transaction exposure.

Likely exposure

Exposure is likely limited to parties holding, integrating, accepting, or auditing Soar Labs Soar Coin based on the referenced vulnerable code. The CVE affected-product fields are nonspecific, so do not assume broader cryptocurrency or wallet exposure without matching this code or contract lineage.

Exploitation context

The CVE itself describes theft as the outcome. A cited BankInfoSecurity article reports a real-world $5 million loss involving a backdoored cryptocurrency. The CVE is not listed as KEV in the provided bundle, and the sources do not establish ongoing active exploitation.

Researcher notes

Evidence is strong for the described backdoor in the named code path, but weak for standardized vulnerability metadata. No CVSS, CWE, CPE, fixed release, or vendor mitigation is present in the bundle. Avoid extrapolating beyond Soar Coin without code or contract matching.

Mitigation direction

  • Stop accepting or transacting with affected Soar Coin code until provenance is confirmed.
  • Check official project or vendor guidance for any replacement, migration, or compensation process.
  • Move business workflows away from unaudited contracts with privileged transfer logic.
  • Preserve transaction, wallet, and integration records for incident review.
  • Require independent smart-contract review before trusting any successor token.

Validation and detection

  • Inventory wallets, exchanges, payment flows, and archives for Soar Coin exposure.
  • Compare deployed or stored source code to the referenced vulnerable commit.
  • Review contract logic for zero_fee_transaction() and onlycentralAccount behavior.
  • Analyze historical transactions for unexpected transfers to the central account.
  • Confirm whether any replacement contract was independently audited before use.
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.

cve · low confidence lookup

CVE-2018-1000203 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.