CyberRota Analysis
AI-GeneratedThe Punk::OAuth2::Server versions up to 0.03 for Perl are vulnerable due to improper handling of access tokens, allowing clients to request tokens with arbitrary scopes outside their registered permissions. This flaw can lead to unauthorized access to resources, as a malicious actor can exploit the system to obtain a valid token for any scope by simply knowing the client ID. Organizations using this OAuth2 server should prioritize remediation to prevent potential exploitation and unauthorized access to sensitive data.
Original NVD Description
Punk::OAuth2::Server versions through 0.03 for Perl issue access tokens outside a client's registered scopes and grant types because no authorization path reads them. Punk::OAuth2::Server::Store registers scopes and grant_types per client and documents both as client registration. token dispatches on the grant_type in the request body, so a client registered for authorization_code alone can ask for client_credentials, and that arm passes the requested scope straight to the minter, which signs it into the at+jwt access token. authorize copies the query scope into the authorization code record without comparing it against the registration, leaving the optional consent hook as the only check between an arbitrary scope and the issued code. redirect_uris on the same client row is read and enforced. A registered client can obtain a correctly signed token carrying any scope it names, and a resource server running Punk::OAuth2::Checker accepts that token and honours the scope. A client registered without a secret authenticates on its client_id alone, so anyone who knows that identifier can request one.