Vulnerability in Azure.Storage.Queues (CVE-2022-30187)
Summary
Vulnerability in Azure.Storage.Queues (CVE-2022-30187). Confidential information can be exposed externally. Mitigation: upgrade to 12.11.0 or later.
Original description
The description as published by the source.
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 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…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2022-30187 has been found in Azure.Storage.Queues.
Confidential information can be exposed externally.
What to do: upgrade Azure.Storage.Queues to 12.11.0 or later.
If unsure, ask your IT team or search "Azure.Storage.Queues CVE-2022-30187" on the vendor's site.
CVE-2022-30187 (Azure.Storage.Queues) — CWE-668
Attack vector: local / no user interaction
Patched: 12.11.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-668) exists in Azure.Storage.Queues.
Check the vendor advisory for the affected versions of Azure.Storage.Queues.
Severity: ?. Confidential information can be exposed externally.
Update to 12.11.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Azure.Storage.Queues' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Azure.Storage.Queues' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Azure.Storage.Queuesを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Azure.Storage.Queues to 12.11.0ステージング環境で 12.11.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web msrc.microsoft.com
- web portal.msrc.microsoft.com