How to fix: Azure Blob upload with container public access
Azure blob uploads that set container access level to 'blob' or 'container' make every object publicly listable. Anonymous enumeration of the container then leaks all uploaded files.
Why it matters
Public containers expose uploaded documents, backups, and user-generated content to anyone who guesses the URL.
The `code-cloud-azure-blob-upload-no-acl` check verifies that the server does not expose the `cloud-azure-blob-upload-no-acl` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Set container access level to 'private' and use SAS tokens or AAD for access.
- 2Generate short-lived user delegation SAS URLs instead of account SAS.
- 3Audit storage account firewalls and disable public network access where possible.
Code examples
Upload Azure blobs with private access only
import { BlobServiceClient } from "@azure/storage-blob";
const client = BlobServiceClient.fromConnectionString(
process.env.AZURE_STORAGE_CONNECTION_STRING!
);
const container = client.getContainerClient("uploads");
// Container must be created with private access
await container.createIfNotExists({ access: undefined }); // no public access
const blob = container.getBlockBlobClient(blobName);
await blob.uploadData(buffer, { blobHTTPHeaders: { blobContentType: mimeType } });References
Detected automatically by VulnRadar. The check id is code-cloud-azure-blob-upload-no-acl, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Azure Blob upload with container public access?
- VulnRadar rates this high severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id code-cloud-azure-blob-upload-no-acl, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Azure Blob upload with container public access map to?
- It maps to CWE-284. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.