🛡️ CVE-2024-58131 — fisco-bcos

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality none, integrity none, availability low.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
• Privileges required: None — an unauthenticated stranger can try it.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Changed — a successful attack reaches components beyond the vulnerable one.
• Confidentiality impact: None.
• Integrity impact: None.
• Availability impact: Low — limited, and the attacker does not choose what is affected.

Weakness class

CVE-2024-58131 is classified as CWE-821: Incorrect Synchronization. The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.

Affected software

CVE-2024-58131 is recorded against 1 package.

• fisco-bcos

Timeline and source

Published on 6 April 2025 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. Record sourced from NVD.

References

github.com
github.com

Other advisories for this package

fisco-bcos has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2022-28937 (7.5 High, published 15 May 2022)
• CVE-2022-28936 (7.5 High, published 15 May 2022)
• CVE-2022-26534 (7.5 High, published 17 Mar 2022)

Same weakness in other software

These advisories are the same class of weakness (CWE-821: Incorrect Synchronization) in other software:

• CVE-2024-7043 (8.0 High, published 7 Jul 2026)
• CVE-2026-56132 (6.9 Medium, published 19 Jun 2026)
• CVE-2026-21919 (6.5 Medium, published 9 Apr 2026)
• CVE-2024-58132 (4.0 Medium, published 6 Apr 2025)
• CVE-2024-58133 (4.0 Medium, published 6 Apr 2025)
• CVE-2024-6657 (6.5 Medium, published 11 Oct 2024)
• CVE-2024-4278 (2.0 Low, published 27 Sep 2024)
• CVE-2024-5755 (5.3 Medium, published 27 Jun 2024)

Details

Affected Packages

References