Microsoft Azure SDK information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic was found in Microsoft Azure SDK. Affected by this vulnerability is an unknown functionality. Executing a manipulation can lead to information disclosure. The identification of this vulnerability is CVE-2024-21421. The attack may be launched remotely. There is no exploit available. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability classified as problematic was found in Microsoft Azure SDK (Cloud Software) (version unknown). This vulnerability affects an unknown function. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.

The weakness was shared 03/12/2024 as confirmed security guidance (Website). The advisory is shared for download at portal.msrc.microsoft.com. This vulnerability was named CVE-2024-21421. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.2

VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 7.5
Vendor Vector (Microsoft): 🔍

CNA Base Score: 7.5
CNA Vector (Microsoft): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

12/08/2023 🔍
03/12/2024 +95 days 🔍
03/12/2024 +0 days 🔍
03/12/2024 +0 days 🔍
04/12/2024 +31 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: portal.msrc.microsoft.com
Status: Confirmed

CVE: CVE-2024-21421 (🔍)
GCVE (CVE): GCVE-0-2024-21421
GCVE (VulDB): GCVE-100-256564

Entryinfo

Created: 03/12/2024 19:45
Updated: 04/12/2024 12:48
Changes: 03/12/2024 19:45 (34), 03/12/2024 19:49 (20), 04/12/2024 12:41 (15), 04/12/2024 12:48 (11)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

 Anonymous User (+0)
2 years ago
Goodmorning,
Could You align this cpe to the cpe "microsoft:windows_azure_sdk"?
I don't find "microsoft:azure_sdk" into cpe NIST Dictioary.
We'd appreciate it very much.
Best Regards,
TEAM CERT
 VulDB Community Team2 years ago
Thank you for your feedback. Unfortunately, this CPE does also not exist. Ours is closest to the one that map to .NET and Java.
 Anonymous User (+0)
2 years ago
The cpe "microsoft:windows_azure_sdk" was used for CVE-2011-1068 Microsoft Windows Azure Software Development Kit.
Could you also append it please?
We would be very grateful.
Best Regards,
TEAM CERT
 VulDB Community Team2 years ago
microsoft:windows_azure_sdk did never exist. We assume it is microsoft:azure_sdk_for_.net or microsoft:azure_sdk_for_java and current microsoft:azure_sdk is closest for pattern matching as of now.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!