LiveActive security incident?Get immediate response
CVE Record

CVE-2021-34273: A security flaw in the 'owned' function of a smart contract implementation for BTC2X (B2X), a tradeable Eth...

A security flaw in the 'owned' function of a smart contract implementation for BTC2X (B2X), a tradeable Ethereum ERC20 token, allows attackers to hijack victim accounts and arbitrarily increase the digital supply of assets.

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

Security readout for executives and security teams

Plain-English summary

CVE-2021-34273 describes a flaw in the owned function of a BTC2X (B2X) ERC20 token smart contract. The reported impact is serious for that token ecosystem: victim account hijack and arbitrary asset supply increase. Sources do not provide CVSS scoring, affected versions, a patch, or confirmation of active exploitation.

Executive priority

Treat this as a targeted crypto-asset exposure review, not a broad enterprise emergency. Priority rises sharply if the organization holds, lists, trades, or integrates BTC2X (B2X), because the reported impact threatens asset control and token supply integrity.

Technical view

The CVE record identifies a vulnerable smart contract implementation for BTC2X (B2X), a tradeable Ethereum ERC20 token. The issue is in the owned function and is reported to affect account control and token supply integrity. No CWE, CPE, version range, contract address, or remediation details are included in the supplied sources.

Likely exposure

Exposure appears limited to organizations, wallets, exchanges, liquidity providers, or services holding, trading, listing, or integrating the specific BTC2X (B2X) ERC20 token implementation. The supplied sources do not identify broader Ethereum, ERC20, or vendor platform exposure.

Exploitation context

The public description says attackers can hijack victim accounts and arbitrarily increase digital asset supply. However, the supplied sources do not cite observed exploitation, CISA KEV listing, exploit maturity, prerequisites, affected contract address, or transaction evidence.

Researcher notes

Evidence is sparse. The CVE names the owned function in a BTC2X smart contract and states severe impact, but lacks CVSS, CWE, CPEs, affected versions, contract address, patch details, and exploitation confirmation. Further analysis should start from the referenced repository and verified on-chain contract data.

Mitigation direction

  • Check current BTC2X project or maintainer guidance for remediation status.
  • Pause new B2X integrations until contract exposure is verified.
  • Review holdings, liquidity pools, and listings tied to the affected token.
  • Assess whether contract migration or delisting controls are needed.
  • Monitor trusted blockchain analytics for abnormal B2X supply or ownership changes.

Validation and detection

  • Identify any BTC2X (B2X) ERC20 contract addresses used by the organization.
  • Confirm whether those addresses match the referenced vulnerable implementation.
  • Review token balances, custody flows, and exchange listings for B2X exposure.
  • Check historical token supply and ownership events for unexplained changes.
  • Document uncertainty where source data lacks affected versions or contract identifiers.
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-2021-34273 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.