Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/NetSPI/FuncoPop
Tools for attacking Azure Function Apps
https://github.com/NetSPI/FuncoPop
Last synced: 25 days ago
JSON representation
Tools for attacking Azure Function Apps
- Host: GitHub
- URL: https://github.com/NetSPI/FuncoPop
- Owner: NetSPI
- License: other
- Created: 2023-07-24T21:59:56.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-10-29T15:41:29.000Z (about 1 month ago)
- Last Synced: 2024-11-11T01:21:30.861Z (about 1 month ago)
- Language: PowerShell
- Size: 4.2 MB
- Stars: 63
- Watchers: 3
- Forks: 6
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[![licence badge]][licence]
[![stars badge]][stars]
[![forks badge]][forks]
[![issues badge]][issues]
[licence badge]:https://img.shields.io/badge/license-New%20BSD-blue.svg
[stars badge]:https://img.shields.io/github/stars/NetSPI/FuncoPop.svg
[forks badge]:https://img.shields.io/github/forks/NetSPI/FuncoPop.svg
[issues badge]:https://img.shields.io/github/issues/NetSPI/FuncoPop.svg
[licence]:https://github.com/NetSPI/FuncoPop/blob/master/LICENSE.txt
[stars]:https://github.com/NetSPI/FuncoPop/stargazers
[forks]:https://github.com/NetSPI/FuncoPop/network
[issues]:https://github.com/NetSPI/FuncoPop/issues
### FuncoPop: PowerShell Tools for Attacking Azure Function Apps
FuncoPop includes functions and scripts that support attacking Azure Funtion Apps, primarily through exploiting Storage Account Access. In many environments, users are granted generous Storage Account permissions (Storage Account Contributor) in Azure RBAC, resulting in access to Storage Accounts that support Function Apps. This unintended cross-service access can give an attacker the ability to pivot through Storage Accounts to gain access to Function Apps. This access includes visibility into the Funtion App keys, ability to run code in the Function App containers, and the ability to access Managed Identities attached to the Function Apps.
These tools were initially released as part of the "What the Function: A Deep Dive into Azure Function App Security" talk from the DEF CON 31 Cloud Village.
### Author, Contributors, and License
* Author:
* Thomas Elling ([@thomaselling](https://twitter.com/thomas_elling)), NetSPI
* Karl Fosaaen ([@kfosaaen](https://twitter.com/kfosaaen)), NetSPI
* License: BSD 3-Clause
* Required Dependencies: Az PowerShell Module
### Tool Usage
There are two parts to this tool - Extraction and Decryption
## Key Extraction
In order to run the key extraction tool, you will need to have an authenticated Azure (Az) PowerShell login with some role that allows Read/Write access to a vulnerable Function App Storage Account. In Powershell, you will need to import the function in order to run it.
**Importing the function:**
`Import-Module .\Invoke-AzFunctionAppTakeover.ps1`
Once imported, you can run the function:
`Invoke-AzFunctionAppTakeover -Verbose`
```
VERBOSE: Currently logged in via Az PowerShell as [email protected]
VERBOSE: Use Connect-AzAccount to change your user
VERBOSE: Dumping Function App information for Selected Subscriptions...
VERBOSE: Enumerating Function App attached Storage Accounts in the TestEnvironment subscription
VERBOSE: Function App Storage Account Found - POCstorageAccount1 - mystarterapp Function App
VERBOSE: Function App Storage Account Found - POCstorageAccount2 - importantbankingapp Function App
VERBOSE: Function App Storage Account Found - POCstorageAccount2 - lessimportantbankingapp Function App
VERBOSE: Function App Storage Account Found - POCstorageAccount3 - managedidentityfunction Function App
[Truncated]
VERBOSE: 15 Function App Storage Accounts Enumerated in the Subscription
VERBOSE: Dumping Function App information for selected Storage Accounts
VERBOSE: Determining Function App Language of the managedidentityfunction function in the POCstorageAccount3 Storage Account
VERBOSE: Reviewing the managedidentityfunctiona16a File Share
VERBOSE: ASP.NET folder found in the managedidentityfunctiona16a File Share
VERBOSE: ASP.NET file found in the site/wwwroot/HttpTrigger1 folder in the managedidentityfunctiona16a File Share
VERBOSE: ASP.NET file found in the site/wwwroot/HttpTrigger2 folder in the managedidentityfunctiona16a File Share
VERBOSE: Attempting to add a new ASP.NET function to the managedidentityfunctiona16a File Share in the POCstorageAccount3 Storage Account
VERBOSE: Creating the MFRgBWvsDIlkyfT folder in the managedidentityfunctiona16a File Share in the POCstorageAccount3 Storage Account and uploading files
VERBOSE: Sleeping for 60 seconds before calling the new function
VERBOSE: Calling the new function (until it stops 404-ing) to return the tokens and decryption key, this may take a while...
VERBOSE: Avoid hitting ctrl+C to break out of this, you will need to manually remove the added Storage Account files in order to clean up
VERBOSE: Removing the files from the Storage Account
VERBOSE: Completed attacking the managedidentityfunction Function App in the managedidentityfunctiona16a File Share
FunctionApp : managedidentityfunction
EncryptedMasterKey : bm9[Truncated]=
EncryptionKey : 1B1[Truncated]9
ManagementToken : eyJ[Truncated]g
VaultToken : eyJ[Truncated]g
GraphToken : eyJ[Truncated]Q
VERBOSE: All Function App / Storage Account attacks have completed
```
The function will prompt you to select a Subscription to attack. Once it has enumerated vulnerable Storage Accounts, you will be prompted with a list of accounts to attack. Select the ones you want to attack and the function will add malicious functions to the Storage Accounts, and attempt to execute them. These malicious functions will return the decryption key for the Function App Master Key, along with Managed Identity tokens (*if available).
Please note that the function supports PowerShell, ASP.NET, Python, and Node for payloads. At this time, attacking Java Function Apps is not supported, but may be added in the future.
Required Module to install:
* Az
## Key Decryption
The easiest way to decrypt the keys returned from the PowerShell function is to run the Function App that we created to do the decryption.
### Host your own Function App to decrypt the keys
Use the following Deploy button to deploy a function app to your Azure subscription that can be used to decrypt the extracted keys.
[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FNetSPI%2FFuncoPop%2Fmain%2Fazuredeploy.json)
### Related Blogs
* What the Function: Decrypting Azure Function App Keys
* Lateral Movement in Azure App Services
### Presentations
* What the Function: A Deep Dive into Azure Function App Security - DEF CON 31 - Cloud Village
- Slides
* What the Function: A Deep Dive into Azure Function App Security - BSides PDX 2024
- Slides
### Previous Research
* Rogier Dijkman - Privilege Escalation via storage accounts
* Roi Nisimi - From listKeys to Glory: How We Achieved a Subscription Privilege Escalation and RCE by Abusing Azure Storage Account Keys
* MSRC - Best practices regarding Azure Storage Keys, Azure Functions, and Azure Role Based Access
* Bill Ben Haim & Zur Ulianitzky - 10 ways of gaining control over Azure function Apps
* Andy Robbins – Abusing Azure App Service Managed Identity Assignments
* Chirag Savla and Raunak Parmar – Abusing Azure Logic Apps – Part 1