Account creation or deletion via missing CSRF validation
Published Jan 13, 2021 · Updated Aug 4, 2024
CSRF in JupyterHub before 1.2.0b1 allows remote authenticated users to add or delete accounts through an administrator session. The admin panel accepts /hub/api/user add and delete requests when the _xsrf field is absent, relying solely on Referer validation. Exploitation requires an authenticated administrator session and browser interaction; the demonstrated consequence is unauthorized account creation or deletion.
Summary
What happened
CSRF in JupyterHub before 1.2.0b1 allows remote authenticated users to add or delete accounts through an administrator session. The admin panel accepts /hub/api/user add and delete requests when the _xsrf field is absent, relying solely on Referer validation. Exploitation requires an authenticated administrator session and browser interaction; the demonstrated consequence is unauthorized account creation or deletion.
The record
- CVE
- CVE-2020-36191
- Published
- Jan 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, CAPEC-62, T1136, T1531
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- Admin-panel missing _xsrf reproductionproof 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