File Upload Security
A file crosses several boundaries—request, parser, storage, scanner, processor and serving path—and each interprets different metadata.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
The system trusts the filename or declared type, processes the file with a privileged library, stores it beside executable content, or accepts unbounded expansion.
The important question is not “what is File Upload Security?” but “which assumption let untrusted data or an over-scoped identity cross untrusted file → parsers, storage and public serving?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Generate storage IDs and isolate non-executable storage Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Generate storage IDs and isolate non-executable storage · Bound compressed and expanded size, then inspect actual type · Process in a sandbox and serve from a separate origin | Scanner findings, parser crashes and size-ratio anomalies | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Service availability, storage integrity and the safety of users who download processed files.
- Boundary: Untrusted file → parsers, storage and public serving
- Primary control: Generate storage IDs and isolate non-executable storage
- Detection signal: Scanner findings, parser crashes and size-ratio anomalies
- Always ask what limits damage when the primary control fails.
Boundary control exercise
This lesson uses the shared boundary-control exercise.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: A user who can upload arbitrary bytes, names and metadata.
- 2The system trusts the filename or declared type, processes the file with a privileged library, stores it beside executable content, or accepts unbounded expansion.
- 3The weak or missing boundary control is crossed: Untrusted file → parsers, storage and public serving
- 4Impact: Parser compromise, stored active content, overwrite, cost exhaustion or malware distribution.
- Parser compromise, stored active content, overwrite, cost exhaustion or malware distribution.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Generate storage IDs and isolate non-executable storage
- • Bound compressed and expanded size, then inspect actual type
- • Process in a sandbox and serve from a separate origin
- • Scanner findings, parser crashes and size-ratio anomalies
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.