Microsoft: CBC Padding Oracle in Azure Blob Storage Encryption Library

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.7 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2022-30187: 0.53% estimated exploitation activity in the next 30 days; percentile 44.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The Azure Storage Encryption library in Java and other languages is vulnerable to a CBC Padding Oracle attack, similar to CVE-2020-8911. The library is not vulnerable to the equivalent of CVE-2020-8912, but only because it currently only supports AES-CBC as encryption mode. Severity Moderate - The vulnerability poses insider risks/privilege escalation risks, circumventing controls for stored data. Further Analysis The Java Azure Blob Storage Encryption SDK is impacted by an issue that can result in loss of confidentiality and message forgery. The attack requires write access to the container in question, and that the attacker has access to an endpoint that reveals decryption failures (without revealing the plaintext) and that when encrypting the CBC option was chosen as content cipher. This advisory describes the plaintext revealing vulnerabilities in the Java Azure Blob Storage Encryption SDK, with a similar issue in the other blob storage SDKs being present as well. In the…

Published by the source

13 Jul 2022, 00:00 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:13 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-64x4-9hc6-r2h6

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-64x4-9hc6-r2h6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-30187

Advisory: Microsoft: CBC Padding Oracle in Azure Blob Storage Encryption Library
IDs: CVE-2022-30187, GHSA-64x4-9hc6-r2h6
Record: https://patchnext.com/advisories/cve-2022-30187 (revision 2, source checked 26 Oct 2026, 13:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: azure.storage.queues 12.11.0; azure-storage-queue 12.4.0; azure.storage.blobs 12.13.0; azure-storage-blob 12.13.0; com.azure:azure-storage-blob 12.18.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet azure.storage.queues: affected < 12.11.0; fixed in 12.11.0
- PyPI azure-storage-queue: affected < 12.4.0; fixed in 12.4.0
- NuGet azure.storage.blobs: affected < 12.13.0; fixed in 12.13.0
- PyPI azure-storage-blob: affected < 12.13.0; fixed in 12.13.0
- Maven com.azure:azure-storage-blob: affected < 12.18.0; fixed in 12.18.0

## Suggested inspection (read-only)
- NuGet azure.storage.queues: check the installed version with your package manager.
- `python -m pip show azure-storage-queue`: prints the installed version. Run with the environment that serves production active.
- NuGet azure.storage.blobs: check the installed version with your package manager.
- `python -m pip show azure-storage-blob`: prints the installed version. Run with the environment that serves production active.
- Maven com.azure:azure-storage-blob: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on azure.storage.queues, azure-storage-queue, azure.storage.blobs, azure-storage-blob, com.azure:azure-storage-blob.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-64x4-9hc6-r2h6 (OSV record GHSA-64x4-9hc6-r2h6 lists affected ranges: NuGet azure.storage.queues >=0 =0 =0 =0 =0 <12.13.0 (fixed))
- Verified: https://github.com/advisories/GHSA-64x4-9hc6-r2h6 (GitHub-reviewed advisory GHSA-64x4-9hc6-r2h6 lists affected ranges: NuGet azure.storage.queues >=0 =0 =0 =0 =0 <12.13.0)

Commands are suggestions: review each one before running it.