Oauthlib : Unsafe JSONP callback injection in RevocationEndpoint allows arbitrary JavaScript response generation

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official description

OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. From 0.6.1 until 4.0.0, OAuthLib's RevocationEndpoint in oauthlib/oauth2/rfc6749/endpoints/revocation.py reflects an unvalidated callback request parameter into success and error response bodies when enable_jsonp=True. The callback can come from the query string or request body and is used without restricting it to a legal JavaScript function name. A browser application that loads the revocation response as trusted JSONP and permits attacker influence over callback can therefore execute attacker-controlled JavaScript in the including application's origin, with access to its DOM and script-accessible data. The feature is disabled by default, so only deployments that explicitly enable JSONP are affected. This issue is fixed in version 4.0.0.

[ Fixes ]Fixes and patches

• oauthlib 4.0.0Fixed version · GitHub Advisories · pip package oauthlib: upgrade to 4.0.0 or later (affected >= 0.6.1, <= 3.3.1)

[ Packages ]Affected open-source packages

• oauthlib pipAffected >= 0.6.1, <= 3.3.1 · fixed in 4.0.0 · GHSA-hj66-6f7g-4r5v

[ References ]References

• github.com/oauthlib/oauthlib/commit/c888359f3c42bec235b2c5caab2069c9ed62457c
• github.com/oauthlib/oauthlib/pull/951
• github.com/oauthlib/oauthlib/releases/tag/v4.0.0
• github.com/oauthlib/oauthlib/security/advisories/GHSA-hj66-6f7g-4r5v