What is CVE-2022-30187?

CVE-2022-30187 is a medium-severity security vulnerability in Azure.Storage.Queues (nuget), affecting versions < 12.11.0. It is fixed in 12.11.0, 12.13.0, 12.18.0, 12.4.0.

How severe is CVE-2022-30187?

CVE-2022-30187 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2022-30187?

Azure.Storage.Queues (nuget) versions < 12.11.0; Azure.Storage.Blobs (nuget) versions < 12.13.0; com.azure:azure-storage-blob (maven) versions < 12.18.0; azure-storage-queue (pip) versions < 12.4.0; azure-storage-blob (pip) versions < 12.13.0.

Is there a fix for CVE-2022-30187?

Yes. CVE-2022-30187 is fixed in 12.11.0, 12.13.0, 12.18.0, 12.4.0. Upgrade to this version or later.

Is CVE-2022-30187 exploitable, and should I be worried?

Whether CVE-2022-30187 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-30187 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2022-30187 in Azure.Storage.Queues

Q: How severe is CVE-2022-30187?

CVE-2022-30187 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2022-30187?

Azure.Storage.Queues (nuget) versions < 12.11.0; Azure.Storage.Blobs (nuget) versions < 12.13.0; com.azure:azure-storage-blob (maven) versions < 12.18.0; azure-storage-queue (pip) versions < 12.4.0; azure-storage-blob (pip) versions < 12.13.0.

Q: Is there a fix for CVE-2022-30187?

Yes. CVE-2022-30187 is fixed in 12.11.0, 12.13.0, 12.18.0, 12.4.0. Upgrade to this version or later.

Q: Is CVE-2022-30187 exploitable, and should I be worried?

Whether CVE-2022-30187 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-30187 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-30187?

Upgrade: Azure.Storage.Queues to 12.11.0 or later, Azure.Storage.Blobs to 12.13.0 or later, com.azure:azure-storage-blob to 12.18.0 or later, azure-storage-queue to 12.4.0 or later, azure-storage-blob to 12.13.0 or later.

Summary

Microsoft: CBC Padding Oracle in Azure Blob Storage Encryption Library

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 current version of the Azure Blob Storage crypto SDK, the only algorithm option that allows users to encrypt files is to AES-CBC, without computing a MAC on the data.

This exposes a padding oracle vulnerability: If the attacker has write access to the blob container bucket and can observe whether or not an endpoint with access to the key can decrypt a file (without observing the file contents that the endpoint learns in the process), they can reconstruct the plaintext with (on average) 128*length(plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors.

Timeline

Date reported: March 29 2022
Date preview: June 16 2022
Date GA: July 11 2022
Date disclosed: July 17 2022

Impact

CVE-2022-30187 has a CVSS score of 4.7 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.11.0, 12.13.0, 12.18.0, 12.4.0); upgrading removes the vulnerable code path.

Affected versions

Azure.Storage.Queues (< 12.11.0) Azure.Storage.Blobs (< 12.13.0) com.azure:azure-storage-blob (< 12.18.0) azure-storage-queue (< 12.4.0) azure-storage-blob (< 12.13.0)

Security releases

Azure.Storage.Queues → 12.11.0 (nuget) Azure.Storage.Blobs → 12.13.0 (nuget) com.azure:azure-storage-blob → 12.18.0 (maven) azure-storage-queue → 12.4.0 (pip) azure-storage-blob → 12.13.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

Azure.Storage.Queues to 12.11.0 or later; Azure.Storage.Blobs to 12.13.0 or later; com.azure:azure-storage-blob to 12.18.0 or later; azure-storage-queue to 12.4.0 or later; azure-storage-blob to 12.13.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-30187? CVE-2022-30187 is a medium-severity security vulnerability in Azure.Storage.Queues (nuget), affecting versions < 12.11.0. It is fixed in 12.11.0, 12.13.0, 12.18.0, 12.4.0.
How severe is CVE-2022-30187? CVE-2022-30187 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2022-30187?
- Azure.Storage.Queues (nuget) (versions < 12.11.0)
- Azure.Storage.Blobs (nuget) (versions < 12.13.0)
- com.azure:azure-storage-blob (maven) (versions < 12.18.0)
- azure-storage-queue (pip) (versions < 12.4.0)
- azure-storage-blob (pip) (versions < 12.13.0)
Is there a fix for CVE-2022-30187? Yes. CVE-2022-30187 is fixed in 12.11.0, 12.13.0, 12.18.0, 12.4.0. Upgrade to this version or later.
Is CVE-2022-30187 exploitable, and should I be worried? Whether CVE-2022-30187 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-30187 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-30187?
- Upgrade Azure.Storage.Queues to 12.11.0 or later
- Upgrade Azure.Storage.Blobs to 12.13.0 or later
- Upgrade com.azure:azure-storage-blob to 12.18.0 or later
- Upgrade azure-storage-queue to 12.4.0 or later
- Upgrade azure-storage-blob to 12.13.0 or later