PYSEC-2018-151
Vulnerability from pysec - Published: 2018-02-18 03:29 - Updated: 2024-11-21 14:22An 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.)
| Name | purl | jupyterhub | pkg:pypi/jupyterhub |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "jupyterhub",
"purl": "pkg:pypi/jupyterhub"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1845c0e4b1bff3462c91c3108c85205acd3c75a2"
}
],
"repo": "https://github.com/jupyterhub/oauthenticator",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.0",
"0.2.0",
"0.3.0",
"0.4.0",
"0.4.1",
"0.5.0",
"0.6.0",
"0.6.1",
"0.7.0",
"0.7.0b1",
"0.7.1",
"0.7.2",
"0.8.0",
"0.8.0b1",
"0.8.0b2",
"0.8.0b3",
"0.8.0b4",
"0.8.0b5",
"0.8.0rc1",
"0.8.0rc2",
"0.8.1",
"0.9.0",
"0.9.0b1",
"0.9.0b2",
"0.9.0b3",
"0.9.0rc1",
"0.9.1",
"0.9.2",
"0.9.3",
"0.9.4",
"0.9.5",
"0.9.6",
"1.0.0",
"1.0.0b1",
"1.0.0b2",
"1.1.0",
"1.1.0b1",
"1.2.0",
"1.2.0b1",
"1.2.1",
"1.2.2",
"1.3.0",
"1.4.0",
"1.4.1",
"1.4.2",
"1.5.0",
"1.5.1",
"2.0.0",
"2.0.0b1",
"2.0.0b2",
"2.0.0b3",
"2.0.0rc1",
"2.0.0rc2",
"2.0.0rc3",
"2.0.0rc4",
"2.0.0rc5",
"2.0.1",
"2.0.2",
"2.1.0",
"2.1.1",
"2.2.0",
"2.2.1",
"2.2.2",
"2.3.0",
"2.3.1",
"3.0.0",
"3.0.0b1",
"3.1.0",
"3.1.1",
"4.0.0",
"4.0.0b1",
"4.0.0b2",
"4.0.1",
"4.0.2",
"4.1.0",
"4.1.1",
"4.1.2",
"4.1.3",
"4.1.4",
"4.1.5",
"4.1.6",
"5.0.0",
"5.0.0b1",
"5.0.0b2",
"5.1.0",
"5.2.0",
"5.2.1"
]
}
],
"aliases": [
"CVE-2018-7206"
],
"details": "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\u0027 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.)",
"id": "PYSEC-2018-151",
"modified": "2024-11-21T14:22:52.286953Z",
"published": "2018-02-18T03:29:00Z",
"references": [
{
"type": "ARTICLE",
"url": "https://blog.jupyter.org/security-fix-for-jupyterhub-gitlab-oauthenticator-7b14571d1f76"
},
{
"type": "FIX",
"url": "https://github.com/jupyterhub/oauthenticator/commit/1845c0e4b1bff3462c91c3108c85205acd3c75a2"
},
{
"type": "WEB",
"url": "https://github.com/jupyterhub/oauthenticator/blob/8499dc2/CHANGELOG.md#073---2018-02-16"
},
{
"type": "ADVISORY",
"url": "https://github.com/jupyterhub/oauthenticator/blob/8499dc2/CHANGELOG.md#073---2018-02-16"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"withdrawn": "2024-11-22T04:37:04Z"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.