Threats Tagged 'cwe-325'

Crux Agent from 1.9.0 before 2.0.3 uses the full SKA bilocation key as the WireGuard preshared key. When a peering session negotiates use of SHA-512, the key produced is 64 bytes instead of the 32 bytes WireGuard requires. The agent does not validate this size; instead it attempts to use the `wg set` command to update the live tunnel, and write the invalid key to the WireGuard configuration file. The update fails, so the live tunnel keeps using its previous preshared key until the tunnel is shut down. The tunnel will fail to start when restarted. For a peer which has never successfully negotiated a 32-byte bilocation key in a Crux C2 organization which has the "Enforce SKA Use" setting turned off, no preshared key will be set for the tunnel. Therefore, an attacker who is able to intercept and store the peer's traffic, and has access (or will have access) to a cryptographically relevant quantum computer, will be able to decrypt the tunnel.

Missing cryptographic step in the DSTU 7624 CCM mode implementation (KCcmBlockCipher) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who can observe encrypted messages of known or chosen content to forge ciphertexts with valid authentication tags, via messages encrypted without associated data. The cause is that the G1 block, which binds the nonce, the message length and the parameter flags into the CBC-MAC, was processed only when associated data was present. Without associated data the tag was a CBC-MAC of the plaintext alone, independent of the nonce. Only applications that use KCcmBlockCipher directly and supply no associated data are affected.

Dell Wyse Management Suite versions prior to 2605.0.3.683 contain a vulnerability due to a missing cryptographic step. This flaw could be exploited by a high privileged attacker with remote access to tamper with information. The vulnerability is identified as CWE-325 and has a high severity rating with a CVSS score of 8. No patch or remediation details are provided in the input data.

CVE-2026-25250 is a medium severity vulnerability in eazsolution EazyFix version 12.9. It involves a security feature bypass due to a missing cryptographic step related to disabling Secure Boot. The vulnerability has a CVSS score of 6.0 and impacts confidentiality and integrity but not availability. There is no official patch or remediation level provided by the vendor as of now. No known exploits are reported in the wild.

TP-Link Kasa smart home devices HS103P3 and HS103P4 v5 have insufficient cryptographic protections in their local communication protocol. This weakness allows an adjacent network attacker to intercept, replay, or forge control messages. Exploitation can lead to unauthorized control of the device, causing state changes, disruption, or denial of service.

Missing cryptographic step in Windows Boot Loader allows an authorized attacker to bypass a security feature locally.

Missing cryptographic step in Windows CryptoAPI allows an authorized attacker to perform tampering locally.

This security update provides a functional equivalent of RHSA-2026:33514. The original Red Hat(R) advisory is available from the Red Hat web site at https://access.redhat.com/errata/RHSA-2026:33514.

Missing cryptographic step in Caliptra Core Firmware (aes_256_gcm_update module) results in an incorrect GCM authentication tag. When the streaming AES-256-GCM API is used with empty AAD, the hardware GHASH accumulator state is not saved after the first update call, causing the final tag to exclude the first batch of processed ciphertext. Ciphertext produced by that call may be modified without the tag reflecting the change. This issue affects Core Runtime Firmware: from 2.0.0 through 2.0.1, 2.1.0.

Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8.1, node:crypto.checkPrime(candidate[, options][, callback]) and crypto.checkPrimeSync(candidate[, options]) ran no Miller-Rabin rounds at all when the caller left options.checks at its default of 0. In that mode, the only test applied to the candidate was trial division by the primes up to 17,863. Any composite whose smallest prime factor exceeds that bound — for example the product of two primes just above it, such as 17,881 × 17,891 — was reported as true ("probably prime"). The same divergence affected the lower-level op_node_check_prime / op_node_check_prime_bytes paths that the polyfill calls into. This vulnerability is fixed in 2.8.1.