OAuthLib: Bearer token can be retrieved as long as client knows a valid client ID for device workflow
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in oauthlib 4.0.1.
OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. From 3.3.0 until 4.0.1, OAuthLib's RFC 8628 device workflow does not require DeviceCodeGrant.validate_token_request to check that the device_code parameter is present and valid. A caller whose client request is accepted by the configured validator and who knows a valid client ID enabled for the device workflow can submit a missing or bogus device code to the token endpoint and obtain a bearer token without completing device authorization. This issue is fixed in version 4.0.1.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| oauthlib | >=3.3.0 <4.0.1 | ||
| pypi: oauthlib | >=3.3.0 <4.0.1 | 4.0.1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in oauthlib (PyPI), strongest first
Embed
A live severity badge for an advisory, README or ticket