Pandora's Container Part 1 Unpacking Azure Container Securit...

[carlospolop]

🤖 Automated Content Update

This PR was automatically generated by the HackTricks News Bot based on a technical blog post.

📝 Source Information

• Blog URL: https://trustedsec.com/blog/pandoras-container-part-1-unpacking-azure-container-security
• Blog Title: Pandora's Container Part 1: Unpacking Azure Container Security
• Suggested Section: Pentesting Cloud > Azure Pentesting > Az - Services > Az - Container Registry, with related attack paths referenced from Az - Container Registry Privesc and a new or expanded Az - Container Registry Post Exploitation section

🎯 Content Summary

Overview

This post demonstrates several Azure Container Registry (ACR) attack paths available after compromising an Azure identity with excessive management-plane or registry data-plane permissions. The techniques abuse legitimate Azure functionality rather than a CVE: enabling and retrieving shared ACR administrator credentials, authenticating through Docker, pulling and dissecting proprietary images for secrets, pushing or replacing images, and modifying ACR Tasks so commands execut...

🔧 Technical Details

ACR administrator credential abuse: When an Azure principal has registry write and credential-listing permissions, check adminUserEnabled, enable the shared administrator account with az acr update ... --admin-enabled true, retrieve its credentials, and authenticate to <registry>.azurecr.io with Docker. This converts Azure control-plane access into reusable registry credentials that can support repository reconnaissance, proprietary image theft, malicious pushes, tag replacement, and destructive deletion.

Container supply-chain hijacking through mutable tags: Registry push access permits an attacker to tag a malicious local image with the exact repository and tag consumed by a deployment and upload it using docker tag followed by docker push. If the workload trusts a mutable tag such as latest, a deployment, update, or restart may retrieve and execute the attac...

🤖 Agent Actions

Done.

Updated:

• src/pentesting-cloud/azure-security/az-post-exploitation/az-container-registry-post-exploitation.md
• src/pentesting-cloud/azure-security/az-post-exploitation/README.md
• src/pentesting-cloud/azure-security/az-services/az-container-registry.md
• src/SUMMARY.md

Added concise ACR post-exploitation coverage for:

• enabling/reusing ACR admin Docker creds
• repository/tag enum and image secret hunting
• mutable-tag supply-chain hijacking
• downstream container compromise after image replacement + restart
• cross-reference to existing ACR Tasks managed-identity privesc

Validation:

• confirmed all added internal refs resolve
• mdbook build could not be run because mdbook is not installed in this environment

---

This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.

📚 Repository Maintenance

• MD files processed: 590
• MD files fixed: 1

All .md files have been checked for proper formatting (headers, includes, etc.).

[carlospolop]

🔗 Additional Context

Original Blog Post: https://trustedsec.com/blog/pandoras-container-part-1-unpacking-azure-container-security

Content Categories: Based on the analysis, this content was categorized under "Pentesting Cloud > Azure Pentesting > Az - Services > Az - Container Registry, with related attack paths referenced from Az - Container Registry Privesc and a new or expanded Az - Container Registry Post Exploitation section".

Repository Maintenance:

• MD Files Formatting: 590 files processed (1 files fixed)

Review Notes:

• This content was automatically processed and may require human review for accuracy
• Check that the placement within the repository structure is appropriate
• Verify that all technical details are correct and up-to-date
• All .md files have been checked for proper formatting (headers, includes, etc.)

Bot Version: HackTricks News Bot v1.0