Summary
Parse Server contains an authorization bypass that allows HTTP Range-based file downloads to skip the afterFind(Parse.File) trigger and related validators on streaming-capable storage adapters.
When Range requests are used against adapters like the default GridFS adapter, files intended to be protected by trigger-based access control or validators (such as requireUser) can be accessed without proper authorization checks.
Affected context
The vulnerability appears in Parse Server deployments that:
- Use storage adapters supporting streaming file downloads (for example, the default GridFS adapter),
- Rely on
afterFind(Parse.File)triggers or built-in validators (such asrequireUser) to enforce access control on files, and - Expose file download endpoints that accept HTTP Range headers.
In such environments, the Range-based code path for file downloads does not consistently invoke the same authorization logic as regular file retrieval.
Exploit preconditions
- Attack surface: Public or internal HTTP(S) endpoints that serve Parse Server file downloads.
- Required access: Ability to send crafted HTTP requests to the file download endpoint; knowledge or ability to guess file identifiers/URLs.
- Trigger point: Issuing HTTP requests that include a
Rangeheader to download files through streaming adapters. - Why exploitation is possible: The streaming download path for Range requests bypasses the
afterFind(Parse.File)trigger and associated validators, so authorization logic that would normally restrict access is not applied to these requests.
Why this happens
The root cause is an inconsistent application of authorization logic across different file download paths.
While standard file retrieval routes invoke the afterFind(Parse.File) trigger and built-in validators, the streaming code path used for HTTP Range requests does not.
This discrepancy creates an authorization bypass scenario mapped to CWE-285: Improper Authorization, where protection mechanisms exist but are not uniformly enforced for all relevant operations.
Conceptually, the system treats Range-based streaming as a lower-level I/O operation and fails to reapply higher-level access control policies before serving file content.
Potential impact
- Unauthorized reading of files that should be protected by trigger-based access control.
- Exposure of sensitive user-generated content or private application assets.
- Circumvention of
requireUseror similar validators that normally restrict file access. - Potential leakage of PII or confidential business data stored as files in Parse Server.
General mitigation guidance
Effective mitigation focuses on consistent enforcement of authorization for all file access paths and on reducing reliance on trigger-only controls:
- Ensure that all file download mechanisms, including streaming and Range-based responses, pass through a unified authorization layer before serving content.
- Design access control so that policy decisions are applied close to the storage abstraction rather than relying solely on high-level triggers.
- Prefer explicit, declarative authorization rules for files (e.g., ACLs, role-based checks) that are evaluated regardless of transport mechanism or HTTP headers.
- Minimize direct exposure of raw file URLs without an application-layer guard that verifies user identity and permissions.
- Apply least-privilege principles at the storage layer, restricting generic read access from untrusted code paths.
These patterns help ensure that new adapters or transport features cannot accidentally bypass existing access control logic.
How teams detect issues like this
Detection can leverage both code-level and behavior-level analysis:
- Static analysis & code review:
- Look for file-serving code paths that handle HTTP
Rangeheaders or streaming responses and verify that they invoke the same authorization routines as standard downloads. - Check adapters and middleware for early-return paths that stream file data without passing through centralized access control checks.
- Review usage of
afterFind(Parse.File)triggers and confirm whether any alternative retrieval methods bypass these triggers. - Runtime & logging strategies:
- Enable detailed access logs for file downloads, including headers and user context, and flag Range-based requests that successfully return content without an authenticated user.
- Monitor for high volumes of partial-content (206) responses to files that are expected to be restricted.
- Security testing:
- Incorporate HTTP Range variations into API tests and authorization test suites, verifying that every file access method requires appropriate permissions.
Automated security review tools or custom linters can be configured to highlight direct streaming reads from storage that are not preceded by explicit authorization checks.

