API authentication bypass via unchecked remote-user header
Published May 15, 2024 · Updated Aug 2, 2024
Improper authentication in Paperless-ngx 2.5.0 through 2.8.5 allows remote authenticated users to access disabled API routes. HttpRemoteUserMiddleware accepted the configured identity header on API paths without checking whether PaperlessRemoteUserAuthentication was enabled. Exposure requires frontend remote-user authentication and a proxy that forwards a claimant-controlled header; successful requests can read or change data within the named user's permissions.
Summary
What happened
Improper authentication in Paperless-ngx 2.5.0 through 2.8.5 allows remote authenticated users to access disabled API routes. HttpRemoteUserMiddleware accepted the configured identity header on API paths without checking whether PaperlessRemoteUserAuthentication was enabled. Exposure requires frontend remote-user authentication and a proxy that forwards a claimant-controlled header; successful requests can read or change data within the named user's permissions.
The record
- CVE
- CVE-2024-35184
- Published
- May 15, 2024
- Updated
- Aug 2, 2024
- Vendor
- Paperless-ngx
- Product
- Paperless-ngx
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.5.0, < 2.8.6
- Affected versionversion=2.5.0 <2.8.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Remote-user header API request demonstrationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo