oauthlib vulnerabilities
A generic, spec-compliant, thorough implementation of the OAuth request-signing logic
- Registry
- PyPI
- Latest
- 4.0.1
- License
- BSD-3-Clause
5 known advisories
The latest version, 4.0.1, is not affected by any of them. Projects on older versions may be.
pip install 'oauthlib>=4.0.1'Is your project on an affected oauthlib?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for oauthlib
OAuthLib: Token grants can use attacker-supplied client_id for authorization after authenticating a different client
- Affected
- <4.0.0
- Fixed in
- 4.0.0
OAuthLib: Bearer token can be retrieved as long as client knows a valid client ID for device workflow
- Affected
- >=3.3.0 <4.0.1
- Fixed in
- 4.0.1
Oauthlib: Timing Attack Vulnerability in PKCE code_verifier Comparison (CWE-208)
- Affected
- >=3.0.0 <4.0.0
- Fixed in
- 4.0.0
Oauthlib : Unsafe JSONP callback injection in RevocationEndpoint allows arbitrary JavaScript response generation
- Affected
- >=0.6.1 <4.0.0
- Fixed in
- 4.0.0
OAuthLib vulnerable to DoS when attacker provides malicious IPV6 URI
- Affected
- >=3.1.1 <3.2.2
- Fixed in
- 3.2.2
Is your oauthlib version vulnerable?
Which of your client projects still run an old oauthlib?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.