Frappe: Improper Authorization in OAuth2 Consent Endpoint
21Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 8.5epss 0.2%
probabilidade de exploração
0.2%top 86% das CVEs
exploração observada
nãonenhuma fonte reporta
Frappe is a full-stack web application framework. Prior to 15.114.0 and 16.26.0, the approve and authorize functions in frappe/integrations/oauth2.py allow the OAuth2 consent flow to proceed without restricting approve to POST, without a csrf_token in frappe/templates/includes/oauth_confirmation.html, and without scoping an active OAuth token check to the requesting client. An attacker can cause an authenticated user to approve an OAuth grant or reuse authorization state for the wrong client, exposing data and permitting actions within the granted scopes. This issue is fixed in versions 15.114.0 and 16.26.0.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Produtos afetados
frappe · frappeReferências
https://github.com/frappe/frappe/commit/336c7d335db762b494acdfe43aea69d459fd51d7https://github.com/frappe/frappe/commit/d7460769f999c68d3121b680119f8724ddd3eb9dhttps://github.com/frappe/frappe/commit/eb9c1446cac13236c6d573b136786db2e46254fahttps://github.com/frappe/frappe/pull/40073https://github.com/frappe/frappe/pull/40700https://github.com/frappe/frappe/pull/40701https://github.com/frappe/frappe/releases/tag/v15.114.0https://github.com/frappe/frappe/releases/tag/v16.26.0https://github.com/frappe/frappe/security/advisories/GHSA-2ph8-x773-8p2x