Jupyter JupyterHub OAuthenticator up to 0.6.1/0.7.2 Access Control access control

Summaryinfo

A vulnerability identified as critical has been detected in Jupyter JupyterHub OAuthenticator up to 0.6.1/0.7.2. The impacted element is an unknown function of the component Access Control. The manipulation leads to access control. This vulnerability is traded as CVE-2018-7206. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Jupyter JupyterHub OAuthenticator up to 0.6.1/0.7.2 and classified as critical. This issue affects some unknown functionality of the component Access Control. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.)

The bug was discovered 02/16/2018. The weakness was shared 02/18/2018 (Website). The advisory is shared at blog.jupyter.org. The identification of this vulnerability is CVE-2018-7206 since 02/17/2018. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 0.6.2 or 0.7.3 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Jupyter

Name

• JupyterHub OAuthenticator

Version

• 0.6.0
• 0.6.1
• 0.7.0
• 0.7.1
• 0.7.2

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion