Private delivery policy bypassed through the origin
A private object is protected at the CDN or application edge but remains accessible directly at an owned origin.
Candidate CWE: CWE-862
Test hypothesis#
Use the same private fixture through the intended protected delivery path and a known owner-supplied origin URL. Compare unauthenticated behavior without changing the resource or following unreviewed redirects.
Evidence required#
Origin ownership, delivery policy, both requests and identical canary bytes retrieved through the unauthorized origin route.
Rule out false positives#
The origin intentionally serves public files, the CDN only supplies performance, or the responses are different resources or authentication pages.
Playbook and command references#
- Object storage, signed URLs and delivery boundaries — Follow one private canary through upload, signing, CDN delivery and expiry without enumerating real objects.
- Azure and GCP: identity, delegation and storage access — Apply provider-specific controls for Azure management/data permissions and SAS, plus GCP service accounts, federation and object ACLs.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.