Security readout for executives and security teams
Plain-English summary
FISCO-BCOS release-3.0.0-rc2 is reported to have a denial-of-service flaw where some transactions may fail to commit. In a blockchain environment, that can undermine transaction reliability and may enable double-spending. The public record does not provide severity scoring, confirmed exploitation, or a named fix.
Executive priority
Treat this as urgent only if FISCO-BCOS release-3.0.0-rc2 is in use, especially in value-bearing systems. Otherwise, track vendor guidance and confirm no exposure.
Technical view
The CVE describes a transaction commitment failure in FISCO-BCOS release-3.0.0-rc2. The reported impact is denial of service and possible double-spending when transactions are not committed successfully. No CVSS, CWE, detailed affected CPEs, patch version, or exploit details are provided in the source bundle.
Likely exposure
Exposure appears limited to deployments running FISCO-BCOS release-3.0.0-rc2. The CVE record does not identify other affected versions or products, so version confirmation is the key exposure step.
Exploitation context
No cited source or KEV entry confirms active exploitation. The description states malicious users may use failed transaction commitment behavior for double-spending, but public evidence in the provided sources is limited.
Researcher notes
Evidence is sparse. The CVE names release-3.0.0-rc2 and describes DoS plus possible double-spending, but lacks root-cause details, scoring, affected-version range, exploit confirmation, and remediation specifics.
Mitigation direction
- Identify whether any environment runs FISCO-BCOS release-3.0.0-rc2.
- Check FISCO-BCOS issue 2124 and vendor release notes for fixed versions.
- Avoid production use of the affected release candidate until vendor guidance is confirmed.
- Increase monitoring for failed, pending, or inconsistent transaction commits.
- Preserve logs and ledger state around suspicious transaction failures.
Validation and detection
- Inventory FISCO-BCOS node versions across production and test environments.
- Confirm whether release-3.0.0-rc2 is deployed anywhere.
- Review transaction commit failure rates for abnormal patterns.
- Reconcile ledger/accounting records for possible duplicate spend outcomes.
- Compare deployed versions with vendor guidance from issue 2124.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2021-46359 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/FISCO-BCOS/FISCO-BCOS/issues/2124CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.