VYPR
Moderate severityNVD Advisory· Published Jul 12, 2022· Updated Jul 8, 2025

Azure Storage Library Information Disclosure Vulnerability

CVE-2022-30187

Description

The Azure Storage Encryption SDK is vulnerable to a CBC padding oracle attack, letting an attacker with write access to a blob container decrypt stored data without the key.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

The Azure Storage Encryption SDK is vulnerable to a CBC padding oracle attack, letting an attacker with write access to a blob container decrypt stored data without the key.

Vulnerability

Overview

The Azure Storage Encryption library (the Java SDK and other language SDKs) contains a vulnerability that enables a CBC padding oracle attack [2]. This class of attack, similar to CVE-2020-8911, allows an attacker to recover plaintext from encrypted data by observing whether decryption succeeds or fails. The library currently only supports AES-CBC as the encryption mode and does not compute a Message Authentication Code (MAC) on the encrypted data, which leaves the ciphertext open to manipulation [2].

Exploitation

Prerequisites and Method

To exploit CVE-2022-30187, an attacker must have write access to the target blob storage container and access to an endpoint that reveals decryption failures (without returning the decrypted plaintext) [2]. With these prerequisites, the attacker can send modified ciphertext to the endpoint and observe padding errors. By exploiting the structure of CBC mode and PKCS#5 padding, the attacker can recover the plaintext block by block, requiring on average 128 queries per byte of plaintext [2].

Impact

An attacker who successfully exploits this vulnerability can learn the contents of encrypted blobs stored in Azure Storage. This is an information disclosure that compromises the confidentiality of the data, even though the attacker does not know the encryption key [2]. The severity is rated as Moderate, though it poses insider risks and can circumvent controls designed to protect stored data [2].

Mitigation

Status

Microsoft released an update to the Azure Storage SDKs on July 11, 2022, and the vulnerability was publicly disclosed on July 17, 2022 [1][2]. Users should update to the latest version of the SDK. No workaround is available other than applying the patch or using a different encryption mode if supported [2].

AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
Azure.Storage.QueuesNuGet
< 12.11.012.11.0
Azure.Storage.BlobsNuGet
< 12.13.012.13.0
com.azure:azure-storage-blobMaven
< 12.18.012.18.0
azure-storage-queuePyPI
< 12.4.012.4.0
azure-storage-blobPyPI
< 12.13.012.13.0

Affected products

34

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

5

News mentions

0

No linked articles in our index yet.