GHSA-384w-5v3f-q499
MEDIUMGHSA-384w-5v3f-q499 is a medium-severity (CVSS 6.3) CWE-863 vulnerability in oauthenticator. O3 Security confirms whether GHSA-384w-5v3f-q499 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Base class whitelist configuration ignored in OAuthenticator
Blast Radius
oauthenticatorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
What goes wrong?
The deprecated (in jupyterhub 1.2) configuration Authenticator.whitelist, which should be transparently mapped to Authenticator.allowed_users with a warning, is instead ignored by OAuthenticator classes, resulting in the same behavior as if this configuration has not been set. If this is the only mechanism of authorization restriction (i.e. no group or team restrictions in configuration) then all authenticated users will be allowed. Provider-based restrictions, including deprecated values such as GitHubOAuthenticator.org_whitelist are not affected.
Who is impacted?
All users of OAuthenticator 0.12.0 and 0.12.1 with JupyterHub 1.2 (JupyterHub Helm chart 0.10.0-0.10.5) who use the admin.whitelist.users configuration in the jupyterhub helm chart or the c.Authenticator.whitelist configuration directly. Users of other deprecated configuration, e.g. c.GitHubOAuthenticator.team_whitelist are not affected.
If you see a log line like this and expect a specific list of allowed usernames:
[I 2020-11-27 16:51:54.528 JupyterHub app:1717] Not using allowed_users. Any authenticated user will be allowed.
you are likely affected.
Patches
- Replacing deprecated
c.Authenticator.whitelist = ...withc.Authenticator.allowed_users = ...avoids the issue. - Update oauthenticator to 0.12.2
- Update jupyterhub helm chart to 0.10.6
If any users have been authorized during this time who should not have been, they must be deleted via the API or admin interface, per the documentation.
Workarounds
Replacing c.Authenticator.whitelist = ... with c.Authenticator.allowed_users = ... avoids the issue.
In the jupyterhub helm chart prior to 0.10.6, this can be done via hub.extraConfig:
auth:
allowedUsers:
- user1
- user2
hub:
extraConfig:
allowedUsers: |
# set new field not exposed in helm chart < 0.10.6
set_config_if_not_none(c.Authenticator, "allowed_users", "auth.allowedUsers")
For more information
If you have any questions or comments about this advisory:
- Open a thread on the Jupyter forum
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | oauthenticator | ≥ 0.12.0&&< 0.12.2 | 0.12.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oauthenticator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update oauthenticator to 0.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-384w-5v3f-q499 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-384w-5v3f-q499 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-384w-5v3f-q499. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-384w-5v3f-q499 in your dependencies?
O3 detects GHSA-384w-5v3f-q499 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.