Reddit NetSec

CVE Database V5

AlienVault OTX General

Exploit-DB RSS Feed

Reddit InfoSec News

ThreatFox MISP Feed

CIRCL OSINT Feed

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack data, resulting in acceptance of an invalid signature. In mbedtls_lms_verify, the return values of the internal Merkle tree functions create_merkle_leaf_value and create_merkle_internal_value are not checked. These functions return an integer that indicates whether the call succeeded or not. If a failure occurs, the output buffer (Tc_candidate_root_node) may remain uninitialized, and the result of the signature verification is unpredictable. When the software implementation of SHA-256 is used, these functions will not fail. However, with hardware-accelerated hashing, an attacker could use fault injection against the accelerator to bypass verification.

CVE-2025-49600 is a medium-severity vulnerability affecting MbedTLS versions from 3.3.0 up to but not including 3.6.4. The issue lies in the mbedtls_lms_verify function, which is responsible for verifying LMS (Leighton-Micali Signature) signatures. Specifically, the vulnerability arises because the function fails to check the return values of internal Merkle tree computation functions, create_merkle_leaf_value and create_merkle_internal_value. These functions return status codes indicating success or failure. If a failure occurs, particularly during hash computations, the output buffer used in signature verification may remain uninitialized. This leads to unpredictable verification results, potentially allowing invalid signatures to be accepted. The vulnerability is exploitable only in scenarios where hardware-accelerated hashing is used because the software SHA-256 implementation does not fail in this manner. An attacker capable of inducing faults in the hardware hash accelerator (e.g., via fault injection techniques) can cause the hash computation to fail silently, bypass the signature verification process, and forge LMS signatures by reusing stale stack data. This flaw compromises the integrity of signature verification, enabling attackers to impersonate legitimate signers or inject malicious data that appears valid. The vulnerability does not impact confidentiality or availability directly but poses a significant risk to data integrity and trustworthiness of cryptographic signatures. The CVSS 3.1 base score is 4.9 (medium), reflecting the complexity of exploitation (requires physical or close access to induce hardware faults), no privileges required, and no user interaction needed. No known exploits are reported in the wild as of the publication date. No patches were linked at the time of reporting, indicating that affected users should monitor for updates and apply them promptly once available.

Detailed information about CVE-2025-49600: CWE-325 Missing Cryptographic Step in Mbed mbedtls affecting Mbed mbedtls. Get real-time updates, technical details, 

CVE-2025-49600: CWE-325 Missing Cryptographic Step in Mbed mbedtls - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2025-49600: CWE-325 Missing Cryptographic Step in Mbed mbedtls

Missing Cryptographic Step vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Cryptanalysis. This issue affects Niagara Framework: before 4.14.2, before 4.15.1, before 4.10.11; Niagara Enterprise Security: before 4.14.2, before 4.15.1, before 4.10.11. Tridium recommends upgrading to Niagara Framework and Enterprise Security versions 4.14.2u2, 4.15.u1, or 4.10u.11.

CVE-2025-3938 identifies a Missing Cryptographic Step vulnerability (CWE-325) in the Tridium Niagara Framework and Niagara Enterprise Security products running on Windows, Linux, and QNX platforms. The Niagara Framework is widely used for building automation and control systems, including HVAC, lighting, and energy management, often deployed in critical infrastructure and commercial buildings. This vulnerability arises from an incomplete or missing cryptographic operation within the framework's security mechanisms, which enables cryptanalysis attacks. Specifically, the flaw allows an attacker with high privileges (PR:H) and network access (AV:N) to perform cryptanalysis that compromises the confidentiality of sensitive data without impacting integrity or availability. The vulnerability affects multiple versions of the Niagara Framework and Enterprise Security prior to versions 4.14.2u2, 4.15.u1, and 4.10u.11, which include the necessary patches. The CVSS v3.1 score is 6.8 (medium severity), reflecting the ease of network exploitation with low attack complexity but requiring privileged access and no user interaction. The scope is changed (S:C), indicating that the vulnerability affects components beyond the initially vulnerable component, potentially impacting the broader system confidentiality. No known exploits are currently reported in the wild, but the potential for cryptanalysis suggests that sensitive data such as credentials, configuration secrets, or communication keys could be exposed if exploited. Given the critical role of the Niagara Framework in building automation and industrial control systems, this vulnerability poses a significant risk to the confidentiality of operational data and could facilitate further attacks if leveraged by threat actors.

Detailed information about CVE-2025-3938: CWE-325 Missing Cryptographic Step in Tridium Niagara Framework affecting Tridium Niagara Framework. Get real-time upd

CVE-2025-3938: CWE-325 Missing Cryptographic Step in Tridium Niagara Framework - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2025-3938: CWE-325 Missing Cryptographic Step in Tridium Niagara Framework

Besu Native contains scripts and tooling that is used to build and package the native libraries used by the Ethereum client Hyperledger Besu. Besu 24.7.1 through 25.2.2, corresponding to besu-native versions 0.9.0 through 1.2.1, have a potential consensus bug for the precompiles ALTBN128_ADD (0x06), ALTBN128_MUL (0x07), and ALTBN128_PAIRING (0x08). These precompiles were reimplemented in besu-native using gnark-crypto's bn254 implementation, as the former implementation used a library which was no longer maintained and not sufficiently performant. The new gnark implementation was initially added in version 0.9.0 of besu-native but was not utilized by Besu until version 0.9.2 in Besu 24.7.1. The issue is that there are EC points which may be crafted which are in the correct subgroup but are not on the curve and the besu-native gnark implementation was relying on subgroup checks to perform point-on-curve checks as well. The version of gnark-crypto used at the time did not do this check when performing subgroup checks. The result is that it was possible for Besu to give an incorrect result and fall out of consensus when executing one of these precompiles against a specially crafted input point. Additionally, homogenous Besu-only networks can potentially enshrine invalid state which would be incorrect and difficult to process with patched versions of besu which handle these calls correctly. The underlying defect has been patched in besu-native release 1.3.0. The fixed version of Besu is version 25.3.0. As a workaround for versions of Besu with the problem, the native precompile for altbn128 may be disabled in favor of the pure-java implementation. The pure java implementation is significantly slower, but does not have this consensus issue.

CVE-2025-30147 is a high-severity vulnerability affecting Hyperledger Besu's native cryptographic library component, besu-native, specifically versions from 0.9.0 up to but not including 1.3.0. Hyperledger Besu is an Ethereum client widely used in enterprise blockchain deployments. The vulnerability arises from a missing cryptographic verification step in the implementation of certain elliptic curve (EC) precompiles: ALTBN128_ADD (0x06), ALTBN128_MUL (0x07), and ALTBN128_PAIRING (0x08). These precompiles are critical for cryptographic operations on the bn254 curve, used in zero-knowledge proofs and other advanced cryptographic protocols within Ethereum. The besu-native library replaced an older, less performant cryptographic library with gnark-crypto's bn254 implementation starting in version 0.9.0. However, gnark-crypto at that time performed subgroup membership checks but did not verify that EC points were actually on the curve. This subtle but critical omission allowed crafted EC points that are in the correct subgroup but not on the curve to be accepted. Consequently, Besu could produce incorrect results when executing these precompiles, leading to consensus failures in the blockchain network. Such consensus bugs can cause network forks or invalid state transitions, which are particularly problematic for homogeneous Besu networks, as they may enshrine invalid blockchain states that patched clients cannot process correctly. The vulnerability was patched in besu-native 1.3.0 and Besu 25.3.0. As an interim mitigation, affected Besu versions can disable the native precompile implementation and revert to a pure Java implementation, which is slower but does not suffer from this consensus issue. The CVSS 4.0 score is 8.7 (high), reflecting the network attack vector, no required privileges or user interaction, and the high impact on integrity due to consensus failures. No known exploits are reported in the wild as of the publication date.

Detailed information about CVE-2025-30147: CWE-325: Missing Cryptographic Step in hyperledger besu-native affecting hyperledger besu-native. Get real-time updat

Title	Severity	Type	Source	Date

Threats Tagged 'cwe-325'

Filter Threats

Threats Tagged 'cwe-325'

Keyboard Shortcuts

Navigation

Search & Filters

UI Controls

Accessibility