What is the CVSS score of CVE-2022-30187?

CVE-2022-30187 has a CVSS 3.1 base score of 4.7 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.5%.

Is there a patch available for CVE-2022-30187?

Yes, a patch is available for CVE-2022-30187. Update the affected software to the latest version immediately.

Azure Storage Blobs CVE-2022-30187

MEDIUM

Use of a Broken or Risky Cryptographic Algorithm (CWE-327)

2022-07-12 secure@microsoft.com

Microsoft Information Disclosure Azure Storage Blobs Azure Storage Queue

4.7

CVSS 3.1 · Vendor: microsoft

Severity by source

Vendor (microsoft) PRIMARY

4.7 MEDIUM

AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Primary rating from Vendor (microsoft) · only source for this CVE.

CVSS VectorVendor: microsoft

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

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Jul 12, 2022 - 23:15 cve.org

MEDIUM 4.7

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

19 maven packages depend on com.azure:azure-storage-blob (14 direct, 5 indirect)
11 pypi packages depend on azure-storage-blob (4 direct, 7 indirect)
3 pypi packages depend on azure-storage-queue (2 direct, 1 indirect)

Ecosystem-wide dependent count for version 12.18.0 and other introduced versions.

DescriptionCVE.org

Azure Storage Library Information Disclosure Vulnerability

AnalysisAI

Azure Storage Library Information Disclosure Vulnerability. Rated medium severity (CVSS 4.7). No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-327. Affected products include: Microsoft Azure Storage Blobs, Microsoft Azure Storage Queue.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.