Skip to content
OpenAdvisories

Weakness (CWE)

CWE-323: Reusing a Nonce, Key Pair in Encryption

Base Incomplete

Nonces should be used for the present occasion and only once.

How to prevent it (2 mitigations)
  1. Implementation

    Refuse to reuse nonce values.

  2. Implementation

    Use techniques such as requiring incrementing, time based and/or challenge response to assure uniqueness of nonces.

Source: MITRE CWE-323

15 results · Clear filters · Feed

  • High 8.4

    Krill login-session tokens reuse their encryption nonce across restarts, so any user who can log in can forge an "admin" token

    The vulnerability is that Krill encrypts every login-session token with a nonce built from a counter that is reset to 0 on every Krill restart, so the same (key, nonce) pair is used again after each restart.

  • High 8.2

    Packet CTR reports a full success length after the counter is exhausted

    In Bouncy Castle for Java LTS before 2.73.13, the native one-shot CTR packet cipher did not check that the requested input length fitted the counter space the IV left. In CTR mode the IV and the block counter share one 16-byte block, so an IV of 13 to 15 byte…

  • High 7.4

    wolfEngine reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record

    wolfEngine before 1.4.1 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce …

  • High 7.4

    wolfProvider reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record

    wolfProvider before 1.2.2 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonc…

  • High 7.4

    ePA 3.x Integration: AES-GCM Nonce Reuse via Frozen VAU Request Counter

    ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany's electronic patient record. Prior to 1.3.0, ePA 3.x Integration leaves request_counter unchanged in app/vau/VAUProtokoll.py while constructing VAU mes…

  • High 7.1

    Reusing a Nonce, Key Pair in Encryption in HLOS

    Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.

  • High 7.7

    Session takeover vulnerability

    We found a chain of combining multiple weaknesses in the product that could allow an attacker to become any user in the backend and access any data: * The payment integration plugins Stripe (included in the core system), pretix-mollie, pretix-oppwa, pretix-bi…

  • High 8.1

    Philips Hue Bridge HomeKit Accessory Protocol Static Nonce Authentication Bypass Vulnerability

    Philips Hue Bridge HomeKit Accessory Protocol Static Nonce Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of Philips Hue Bridge. Authentication is not required to ex…

  • High 8.2

    RustDesk Encrypts Local Passwords with World-Readable Machine ID and Fixed Zero Nonce (XSalsa20-Poly1305)

    Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'), Use of Password Hash With Insufficient Computational Effort vulnerability in rustdesk-client RustDesk Client rustdesk, hbb_common on Windows, MacOS, Linux (Password sec…

  • High 8.7

    strongMan vulnerable to private credential recovery due to key and counter reuse

    strongMan is a management interface for strongSwan, an OpenSource IPsec-based VPN. When storing credentials in the database (private keys, EAP secrets), strongMan encrypts the corresponding database fields. So far it used AES in CTR mode with a global databas…

  • High 7.4

    Improper management of a static JWT signing secret in the web application, where the secret lacks rotation , introducing a security risk

    HCL MyXalytics  is affected by improper management of a static JWT signing secret in the web application, where the secret lacks rotation , introducing a security risk

  • High 8.4

    Reusing a Nonce, Key Pair in Encryption in Automotive Platform

    Cryptographic issue may occur while encrypting license data.

  • High 7.2

    Johnson Controls IQ Panels2, 2+, IQHub, IQPanel 4, PowerG reusing a nonce, key pair in encryption

    Due to Nonce reuse, attackers can perform reply attack or decrypt captured packets.

  • High 8.8

    Keystream recovery for arbitrary frames in TETRA

    Adversary-induced keystream re-use on TETRA air-interface encrypted traffic using any TEA keystream generator. IV generation is based upon several TDMA frame counters, which are frequently broadcast by the infrastructure in an unauthenticated manner. An activ…

  • High 8.6

    Inbound TCP Agent Protocol/3 authentication bypass in Jenkins

    Jenkins 2.213 and earlier, LTS 2.204.1 and earlier improperly reuses encryption key parameters in the Inbound TCP Agent Protocol/3, allowing unauthorized attackers with knowledge of agent names to obtain the connection secrets for those agents, which can be u…