p PatchFirst

CVE-2023-2975

CVE-2023-2975 · AES-SIV implementation ignores empty associated data entries

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence. Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be misled by removing, adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications. The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated. As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue.

CVSS 5.3 · Medium · EPSS 0.6% · Fix available

Published
Updated

Stack: system · network

Affected products and versions

  • openssl

    Versions
    • ≥ 3.1.0, < 3.1.2: Affected (semver)
    • ≥ 3.0.0, < 3.0.10: Affected (semver)

    Update to 3.0.10; Update to 3.1.2

  • openssl Debian:12

    Versions
    • 3.0.9-1
    Affected ranges
    • ECOSYSTEM: < 3.0.10-1~deb12u1

    Update to 3.0.10-1~deb12u1

  • openssl Debian:13

    Affected ranges
    • ECOSYSTEM: < 3.0.10-1

    Update to 3.0.10-1

  • openssl Debian:14

    Affected ranges
    • ECOSYSTEM: < 3.0.10-1

    Update to 3.0.10-1

  • openssl Ubuntu:22.04:LTS

    Versions
    • 1.1.1l-1ubuntu1
    • 3.0.0-1ubuntu1
    • 3.0.1-0ubuntu1
    • 3.0.2-0ubuntu1
    • 3.0.2-0ubuntu1.1
    • 3.0.2-0ubuntu1.2
    • 3.0.2-0ubuntu1.4
    • 3.0.2-0ubuntu1.5
    • 3.0.2-0ubuntu1.6
    • 3.0.2-0ubuntu1.7
    • 3.0.2-0ubuntu1.8
    • 3.0.2-0ubuntu1.9
    • 3.0.2-0ubuntu1.10
    Affected ranges
    • ECOSYSTEM: < 3.0.2-0ubuntu1.12

    Update to 3.0.2-0ubuntu1.12

  • nodejs Ubuntu:Pro:22.04:LTS

    Versions
    • 12.22.5~dfsg-5ubuntu1
    • 12.22.7~dfsg-2ubuntu1
    • 12.22.7~dfsg-2ubuntu3
    • 12.22.9~dfsg-1ubuntu2
    • 12.22.9~dfsg-1ubuntu3
    • 12.22.9~dfsg-1ubuntu3.1
    • 12.22.9~dfsg-1ubuntu3.2
    • 12.22.9~dfsg-1ubuntu3.3
    • 12.22.9~dfsg-1ubuntu3.4
    • 12.22.9~dfsg-1ubuntu3.5
    • 12.22.9~dfsg-1ubuntu3.6
    • 12.22.9~dfsg-1ubuntu3.6+esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • openssl Ubuntu:Pro:FIPS-preview:22.04:LTS

    Versions
    • 3.0.2-0ubuntu1.10+Fips1
    Affected ranges
    • ECOSYSTEM: < 3.0.2-0ubuntu1.12+Fips1

    Update to 3.0.2-0ubuntu1.12+Fips1

  • openssl Ubuntu:Pro:FIPS-updates:22.04:LTS

    Versions
    • 3.0.2-0ubuntu1.10+Fips1
    Affected ranges
    • ECOSYSTEM: < 3.0.2-0ubuntu1.12+Fips1

    Update to 3.0.2-0ubuntu1.12+Fips1

Original sources

Check your server →