Oauthenticator vulnerabilitiesRanked by how likely they are to be used.
Oauthenticator is made by Jupyter. We track 3 published vulnerabilities in it, across 26 versions. None of them is on the list of flaws known to be exploited today. If you run Oauthenticator, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Oauthenticator vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Oauthenticator's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Oauthenticator flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.8%CVE-2018-7206High
An issue was discovered in Project Jupyter JupyterHub OAuthenticator 0.6.x before 0.6.2 and 0.7.x before 0.7.3.
- 1.1%CVE-2020-26250Medium
OAuthenticator is an OAuth login mechanism for JupyterHub.
- 0.5%CVE-2022-31027Medium
OAuthenticator is an OAuth token library for the JupyerHub login handler.
Running Oauthenticator? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
An issue was discovered in Project Jupyter JupyterHub OAuthenticator 0.6.x before 0.6.2 and 0.7.x before 0.7.3. When using JupyterHub with GitLab group whitelisting for access control, group membership was not checked correctly, allowing members not in the whitelisted groups to create accounts on the Hub. (Users were not allowed to access other users' accounts, but could create their own accounts on the Hub linked to their GitLab account. GitLab authentication not using gitlab_group_whitelist is unaffected. No other Authenticators are affected.)
- Matched to
- Oauthenticator on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 3 published vulnerabilities listed under the name Oauthenticator, across 26 versions.
None of Oauthenticator's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Oauthenticator. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.