Microsoft Power Automate/Power Apps/Power BI SAS URI 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.
3.0$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Microsoft Power Automate, Power Apps and Power BI. This affects an unknown part of the component SAS URI Handler. The manipulation leads to information disclosure. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. It is recommended to disable the affected component.

Detailsinfo

A vulnerability was found in Microsoft Power Automate, Power Apps and Power BI (Automation Software) (affected version unknown) and classified as problematic. This issue affects an unknown functionality of the component SAS URI Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.

The weakness was shared 11/17/2022. The advisory is shared at github.com. The advisory contains:

Shared access signatures (SAS) are web addresses (URI) that are temporarily valid (e.g., for 2 days) and grant any user, who is in possession of the URI, access to the respective cloud storage resource (e.g., a specific file with classified data). Our tests on Microsoft Power Apps, Power BI and Power Automate showed that SAS URIs are not only manually created by users but are also automatically created by the cloud applications in the background. This potentially leads to a high number of temporarily valid SAS URIs. Furthermore, the creation of SAS URIs is not logged/audited (see separate vulnerability report) and as a result, there is zero visibility.
Shared access signatures (SAS) are web addresses (URI) that are temporarily valid (e.g., for 2 days) and grant any user, who is in possession of the URI, access to the respective cloud storage resource (e.g., a specific file with classified data). Our tests on Microsoft Power Apps, Power BI and Power Automate showed that SAS URIs are not only manually created by users but are also automatically created by the cloud applications in the background. This potentially leads to a high number of temporarily valid SAS URIs. Furthermore, the creation of SAS URIs is not logged/audited (see separate vulnerability report) and as a result, there is zero visibility. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The exploit is available at github.com. It is declared as proof-of-concept.

The best possible mitigation is suggested to be disabling the affected component. The advisory contains the following remark:

Microsoft closed case. "MSRC has investigated this issue and concluded that this does not pose an immediate threat that requires urgent attention due to low impact."

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.1
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Disable
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/17/2022 🔍
11/17/2022 +0 days 🔍
11/17/2022 +0 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: github.com
Status: Confirmed

GCVE (VulDB): GCVE-100-213809
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 11/17/2022 09:01
Changes: 11/17/2022 09:01 (28), 11/17/2022 09:03 (18)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!