Skip to content

Commit 15a76b9

Browse files
committed
apps username
1 parent 9584fa4 commit 15a76b9

3 files changed

Lines changed: 13 additions & 1 deletion

File tree

src/pentesting-cloud/azure-security/az-privilege-escalation/az-app-services-privesc.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -129,9 +129,15 @@ Note how the **credentials are the same** as in the previous command.
129129
- Another option would be to **set you own creds** and use them:
130130

131131
```bash
132+
# Show if any user is configured (password won't be shown)
133+
az webapp deployment user show
134+
135+
# Set your own credentials
132136
az webapp deployment user set \
133137
--user-name hacktricks \
134138
--password 'W34kP@ssw0rd123!'
139+
140+
# To delete it, check https://stackoverflow.com/questions/45275329/remove-deployment-credentials-from-azure-webapp
135141
```
136142

137143
Then, you can use this credentials to **access the SCM and FTP platforms**. This is also a great way to maintain persistence.

src/pentesting-cloud/azure-security/az-services/az-app-services.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -180,6 +180,10 @@ az webapp conection list --name <name> --resource-group <res-group>
180180

181181
# Get hybrid-connections of a webapp
182182
az webapp hybrid-connections list --name <name> --resource-group <res-group>
183+
184+
# Get configured SMC users by your account
185+
az webapp deployment user show
186+
## If any user is created, the username should appear in the "publishingUserName" field
183187
```
184188

185189
{{#endtab }}

src/pentesting-cloud/azure-security/az-services/az-function-apps.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,9 @@ The **system assigned** one will be a managed identity that **only the function*
6767
6868
It's possible to use the [**PEASS scripts**](https://github.com/peass-ng/PEASS-ng) to get tokens from the default managed identity from the metadata endpoint. Or you could get them **manually** as explained in:
6969

70-
{% embed url="https://book.hacktricks.wiki/en/pentesting-web/ssrf-server-side-request-forgery/cloud-ssrf.html#azure-vm" %}
70+
{{#ref}}
71+
https://book.hacktricks.wiki/en/pentesting-web/ssrf-server-side-request-forgery/cloud-ssrf.html#azure-vm
72+
{{#endref}}
7173

7274
Note that you need to find out a way to **check all the Managed Identities a function has attached** as if you don't indicate it, the metadata endpoint will **only use the default one** (check the previous link for more info).
7375

0 commit comments

Comments
 (0)