Lookup for vulnerable packages by Package URL.
| Purl | pkg:pypi/oauthenticator@0.6.2 |
|---|
| Type | pypi |
|---|
| Namespace | |
|---|
| Name | oauthenticator |
|---|
| Version | 0.6.2 |
|---|
| Qualifiers |
|
|---|
| Subpath | |
|---|
| Is_vulnerable | true |
|---|
| Next_non_vulnerable_version | 16.3.1 |
|---|
| Latest_non_vulnerable_version | 17.4.0 |
|---|
| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-f12e-7kyd-cyhg |
| vulnerability_id |
VCID-f12e-7kyd-cyhg |
| summary |
OAuthenticator is an OAuth token library for the JupyerHub login handler. CILogonOAuthenticator is provided by the OAuthenticator package, and lets users log in to a JupyterHub via CILogon. This is primarily used to restrict a JupyterHub only to users of a given institute. The allowed_idps configuration trait of CILogonOAuthenticator is documented to be a list of domains that indicate the institutions whose users are authorized to access this JupyterHub. This authorization is validated by ensuring that the *email* field provided to us by CILogon has a *domain* that matches one of the domains listed in `allowed_idps`.If `allowed_idps` contains `berkeley.edu`, you might expect only users with valid current credentials provided by University of California, Berkeley to be able to access the JupyterHub. However, CILogonOAuthenticator does *not* verify which provider is used by the user to login, only the email address provided. So a user can login with a GitHub account that has email set to `<something>@berkeley.edu`, and that will be treated exactly the same as someone logging in using the UC Berkeley official Identity Provider. The patch fixing this issue makes a *breaking change* in how `allowed_idps` is interpreted. It's no longer a list of domains, but configuration representing the `EntityID` of the IdPs that are allowed, picked from the [list maintained by CILogon](https://cilogon.org/idplist/). Users are advised to upgrade. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2022-31027, GHSA-r7v4-jwx9-wx43, GMS-2022-1894, PYSEC-2022-206
|
| risk_score |
3.1 |
| exploitability |
0.5 |
| weighted_severity |
6.2 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-f12e-7kyd-cyhg |
|
| 1 |
| url |
VCID-sfqk-pqmp-nkfj |
| vulnerability_id |
VCID-sfqk-pqmp-nkfj |
| summary |
Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0
JupyterHub < 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. The configuration for this would look like:
```python |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2024-37300, GHSA-gprj-3p75-f996
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-sfqk-pqmp-nkfj |
|
| 2 |
| url |
VCID-zb4n-rxh3-bbd9 |
| vulnerability_id |
VCID-zb4n-rxh3-bbd9 |
| summary |
GoogleOAuthenticator.hosted_domain incorrectly verifies membership of an Google organization/workspace
[`GoogleOAuthenticator.hosted_domain`] is used to restrict what Google accounts can be authorized to access a JupyterHub. The restriction _is intended_ to ensure Google accounts are part of one or more Google organizations/workspaces verified to control specified domain(s).
The vulnerability is that the actual restriction has been to Google accounts with emails ending with the domain. Such accounts could have been created by anyone which at one time was able to read an email associated with the domain. This was described by Dylan Ayrey (@dxa4481) in this [blog post] from 15th December 2023. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2024-29033, GHSA-55m3-44xf-hg4h
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-zb4n-rxh3-bbd9 |
|
|
|---|
| Fixing_vulnerabilities |
| 0 |
| url |
VCID-zn45-t3yy-p7gf |
| vulnerability_id |
VCID-zn45-t3yy-p7gf |
| summary |
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.) |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2018-7206, GHSA-8x3m-m3x9-54fj, PYSEC-2018-151, PYSEC-2018-68
|
| risk_score |
4.0 |
| exploitability |
0.5 |
| weighted_severity |
8.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-zn45-t3yy-p7gf |
|
|
|---|
| Risk_score | 3.1 |
|---|
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:pypi/oauthenticator@0.6.2 |
|---|