Cyber Resilience

CVE-2024-58131

Fisco-Bcos 3.11.0

Public PoC
Published
06 April 2025
Modified
08 April 2025
CVSS Score v3.1 4.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L
EPSS Score 0.0025 17th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2024-58131 is a medium-severity Incorrect Synchronization (CWE-821) vulnerability in Fisco-Bcos Fisco-Bcos. Its CVSS base score is 4.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

FISCO BCOS 3.11.0 has an issue with synchronization of the transaction pool that can, for example, be observed when a malicious node (that has modified the codebase to allow a large min_seal_time value) joins a blockchain network.

CWE(s)
CWE-821CWE-662

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-5088Shared CWE-662, CWE-821
CVE-2024-7409Shared CWE-662
CVE-2025-27104Shared CWE-662
CVE-2025-22853Shared CWE-662
CVE-2024-32644Shared CWE-662
CVE-2026-56132Shared CWE-821
CVE-2024-6657Shared CWE-821
CVE-2026-21919Shared CWE-821
CVE-2024-4278Shared CWE-821
CVE-2024-58132Shared CWE-821

Affected Assets

fisco-bcos
fisco-bcos
3.11.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.1
  • V6.5.1
  • V15.1.3
  • V15.4.2

Mitigating Controls (NIST 800-53 r5) AI

SC-39 Process Isolation partial match

Process isolation reduces the attack surface and blast radius of synchronization failures but does not itself implement the required synchronization.

SC-4 Information in Shared System Resources partial match

SC-4 directly requires preventing unintended information transfer through shared resources, structurally blocking the concurrent unsynchronized access described by CWE-821.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require correct concurrency controls and synchronization primitives to prevent race conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect synchronization flaws before production deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices include concurrency and synchronization requirements that reduce race conditions.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate proper locking and thread-safety controls.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles address concurrent access and resource synchronization.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require correct synchronization primitives and thread-safety.

A.8.32 Change management none match
none

Change management processes can introduce or miss synchronization fixes during updates.

References