CVE-2022-31027

{"id": "CVE-2022-31027", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 4.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:S/C:P/I:N/A:N", "authentication": "SINGLE", "integrityImpact": "NONE", "accessComplexity": "LOW", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.2, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 2.5, "exploitabilityScore": 1.6}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.8}]}, "published": "2022-06-09T13:15:08.527", "references": [{"url": "https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-r7v4-jwx9-wx43", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-r7v4-jwx9-wx43", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-639"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "OAuthenticator es una biblioteca de tokens OAuth para el administrador de inicio de sesi\u00f3n de JupyerHub. CILogonOAuthenticator es proporcionado por el paquete OAuthenticator, y permite a usuarios iniciar sesi\u00f3n en un JupyterHub por medio de CILogon. Es usado principalmente para restringir un JupyterHub s\u00f3lo a usuarios de un determinado instituto. El rasgo de configuraci\u00f3n allowed_idps de CILogonOAuthenticator est\u00e1 documentado para ser una lista de dominios que indican las instituciones cuyos usuarios est\u00e1n autorizados a acceder a este JupyterHub. Esta autorizaci\u00f3n es comprobada al asegurarse de que el campo *email* que nos proporciona CILogon presenta un *dominio* que coincide con uno de los dominios listados en \"allowed_idps\".Si \"allowed_idps\" contiene \"berkeley.edu\", se podr\u00eda esperar que s\u00f3lo usuarios con credenciales v\u00e1lidas actuales proporcionadas por la Universidad de California, Berkeley, puedan acceder al JupyterHub. Sin embargo, CILogonOAuthenticator *no* verifica qu\u00e9 proveedor usa el usuario para iniciar sesi\u00f3n, s\u00f3lo la direcci\u00f3n de correo electr\u00f3nico proporcionada. As\u00ed que un usuario puede iniciar sesi\u00f3n con una cuenta de GitHub que tenga el correo electr\u00f3nico configurado como \"(something)@berkeley.edu\", y eso ser\u00e1 tratado exactamente igual que alguien que inicie sesi\u00f3n usando el proveedor de identidad oficial de UC Berkeley. El parche que corrige este problema hace un *cambio radical* en la interpretaci\u00f3n de \"allowed_idps\". Ya no es una lista de dominios, sino una configuraci\u00f3n que representa el \"EntityID\" de los IdPs que est\u00e1n permitidos, escogidos de la [lista mantenida por CILogon](https://cilogon.org/idplist/). Es recomendado a usuarios actualizar"}], "lastModified": "2024-11-21T07:03:44.520", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:jupyter:oauthenticator:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "060B73F9-BCFA-4C4D-B119-11AD934D61EA", "versionEndExcluding": "15.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}