oauthlib 3.3.1
PkgFire would install this release with a warning.·Checked 29 minutes ago·Published 19 June 2025
Why
-
warnVulnerability
Oauthlib : Unsafe JSONP callback injection in RevocationEndpoint allows arbitrary JavaScript response generation (fixed in 4.0.0)
-
warnVulnerability
Oauthlib: Timing Attack Vulnerability in PKCE code_verifier Comparison (CWE-208) (fixed in 4.0.0)
-
warnVulnerability
OAuthLib: Bearer token can be retrieved as long as client knows a valid client ID for device workflow (fixed in 4.0.0)
-
warnVulnerability
OAuthLib: Token grants can use attacker-supplied client_id for authorization after authenticating a different client (fixed in 4.0.0)
-
warnVulnerability
Oauthlib : Unsafe JSONP callback injection in RevocationEndpoint allows arbitrary JavaScript response generation (fixed in 4.0.0)
-
warnVulnerability
Oauthlib: Timing Attack Vulnerability in PKCE code_verifier Comparison (CWE-208) (fixed in 4.0.0)
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Not signed
- Build provenance
- Attested
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.