Azure Storage Account Allows Anonymous Blob Access

The storage account permits anonymous read access to blob containers, so anyone who knows or guesses a container's address can read, and sometimes list, the files in it.

SeverityHigh
CVSS 3.17.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Open in the calculator
CVSS 4.08.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-552: Files or Directories Accessible to External Parties
OWASP Top 10A01:2025 Broken Access Control
MITRE ATT&CKT1530 Data from Cloud Storage, T1619 Cloud Storage Object Discovery
CategoryBroken Access Control

Description

Azure Blob Storage can serve data to clients that present no credentials at all. Two settings control this: the storage account's AllowBlobPublicAccess property (Allow Blob anonymous access in the portal) must permit it, and each container then has its own anonymous access level. A container set to the Blob level lets anyone read a file whose name they know, and a container set to the Container level also lets anyone list every file it holds.

An unauthenticated attacker can therefore download every file in a public container without needing any credential. Storage account and container names are often guessable from the organisation's name and environment names, and tools such as MicroBurst enumerate both. Exposed containers commonly hold backups, database exports, logs, documents and configuration files, and configuration files often contain further secrets, such as connection strings or storage account keys, that widen the attacker's access. The impact depends on what the containers hold: a container of intentionally public images matters little, while one holding personal data may also amount to a reportable data breach. Anonymous access is read only, so it does not by itself let an attacker change or delete data.

Storage accounts created recently disallow anonymous access by default, so the finding is most common on older accounts, on accounts deployed from templates that enable the property, and on accounts where a container was made public deliberately for website assets and later used for other data.

The weakness is confirmed by sending an unauthenticated request for a container on the account's blob endpoint, adding ?restype=container&comp=list to ask for a listing, and by downloading files without credentials. Microsoft Defender for Cloud and cloud posture tools report accounts that permit anonymous access.

Remediation

Disallow anonymous access at the account level, which overrides every container's own setting:

  • Set Allow Blob anonymous access to Disabled in the storage account's Configuration settings, and set allowBlobPublicAccess to false in the templates and scripts that deploy it.
  • Before the change, check whether any client legitimately depends on anonymous reads: the account's transaction metrics can be split by authentication type to show anonymous requests.
  • Where content genuinely must be public, keep it in a dedicated storage account that holds nothing else, or give clients time-limited shared access signatures, preferably user delegation SAS tokens.
  • Prevent recurrence with an Azure Policy assignment, at management group level, that audits or denies storage accounts permitting anonymous blob access.
  • Treat anything that was exposed as disclosed: review the account's logs for anonymous reads where logging was enabled, and rotate any secrets found in the exposed files.

With the Azure CLI:

az storage account update --name "$ACCOUNT" --resource-group "$RG" --allow-blob-public-access false

As an interim measure, set the access level of each public container to Private. Confirm the fix by repeating the unauthenticated listing and download requests and confirming that they are refused.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Azure and Microsoft 365 Findings

Every Azure and Microsoft 365 finding