doorkeeper 5.2.0.rc3
Doorkeeper Improper Authentication vulnerability
medium severity CVE-2023-34246>= 5.6.6
OAuth RFC 8252 says https://www.rfc-editor.org/rfc/rfc8252#section-8.6
the authorization server SHOULD NOT process authorization requests automatically without user consent or interaction, except when the identity of the client can be assured. This includes the case where the user has previously approved an authorization request for a given client id
But Doorkeeper automatically processes authorization requests without user consent for public clients that have been previous approved. Public clients are inherently vulnerable to impersonation, their identity cannot be assured.
Issue https://github.com/doorkeeper-gem/doorkeeper/issues/1589
Doorkeeper application secret information disclosure vulnerability
medium severity CVE-2020-10187~> 5.0.3, ~> 5.1.1, ~> 5.2.5, >= 5.3.2
< 5.0.0
Information disclosure vulnerability. Allows an attacker to see all Doorkeeper::Application model attribute values (including secrets) after authorizing an application to their user.
An application is vulnerable if the authorized applications controller is enabled (GET /oauth/authorized_applications.json).
Recommended additional hardening for >= 5.1 is to enable application secrets hashing. This would render the exposed secret useless.
No officially reported memory leakage issues detected.
This gem version does not have any officially reported memory leaked issues.
No license issues detected.
This gem version has a license in the gemspec.
This gem version is available.
This gem version has not been yanked and is still available for usage.