Falhas do tipo CWE-863

3.814 resultados

Falha em verificação de autorização

O software realiza uma verificação de autorização, mas a implementação está incorreta ou incompleta, permitindo que um atacante contorne as restrições de acesso pretendidas. O erro típico é lógica falha na verificação (condições mal formuladas, casos não tratados) ou confiança em dados do usuário para validar permissões.

Exemplo

Uma aplicação web valida se o usuário está autenticado, mas esquece de checar se ele tem permissão para acessar o recurso específico. Um atacante muda o ID do objeto na URL e acessa dados de outro usuário porque a aplicação não verifica propriedade ou role antes de retornar o conteúdo.

Como mitigar

Implemente verificações de autorização explícitas em todo ponto de acesso a recurso sensível, verificando não apenas quem é o usuário, mas se ele tem permissão específica para aquela ação. Use um modelo de controle de acesso bem definido (RBAC, ABAC) e teste sistematicamente casos de bypass (usuários não autorizados, escalação de privilégio, alteração de parâmetros).

CVE-2023-38389CRITICALWordPress Jupiter X Core plugin <= 3.3.8 - Unauthenticated Account Takeover vulnerabilityEPSS 1.4%CVE-2023-6152MEDIUMA user changing their email after signing up and verifying it can change it without verification in profile settings. The configuration optEPSS 1.4%CVE-2021-4133—A flaw was found in Keycloak in versions from 12.0.0 and before 15.1.1 which allows an attacker with any existing user account to create newEPSS 1.4%CVE-2024-29834MEDIUMApache Pulsar: Improper Authorization For Namespace and Topic Management EndpointsEPSS 1.4%CVE-2022-42344HIGH[CVE-2021-36032] Magento IDOR Leads to Account TakeoverEPSS 1.3%CVE-2021-38312HIGHGutenberg Template Library & Redux Framework <= 4.2.11 Incorrect Authorization check to Arbitrary plugin installation and post deletionEPSS 1.3%CVE-2019-6836—A CWE-863: Incorrect Authorization vulnerability exists in U.motion Server (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX EPSS 1.3%CVE-2021-24717—AutomatorWP < 1.7.6 - Missing Authorization and Privilege EscalationEPSS 1.3%CVE-2023-40610MEDIUMApache Superset: Privilege escalation with default examples databaseEPSS 1.3%CVE-2024-27139HIGHApache Archiva: incorrect authentication potentially leading to account takeoverEPSS 1.3%CVE-2022-45544HIGHInsecure Permission vulnerability in Schlix Web Inc SCHLIX CMS 2.2.7-2 allows attacker to upload arbitrary files and execute arbitrary code EPSS 1.3%CVE-2021-20282—When creating a user account, it was possible to verify the account without having access to the verification email link/secret in moodle beEPSS 1.3%CVE-2023-31704—Sourcecodester Online Computer and Laptop Store 1.0 is vulnerable to Incorrect Access Control, which allows remote attackers to elevate privEPSS 1.3%CVE-2026-97380HIGHMariaDB: GRANT PROXY with empty password incorrectly checks grantor's privilegesEPSS 1.3%CVE-2025-27696MEDIUMApache Superset: Incorrect authorization leading to resource ownership takeoverEPSS 1.3%CVE-2022-1706—A vulnerability was found in Ignition where ignition configs are accessible from unprivileged containers in VMs running on VMware products. EPSS 1.3%CVE-2022-23452—An authorization flaw was found in openstack-barbican, where anyone with an admin role could add secrets to a different project container. TEPSS 1.3%CVE-2022-0670—A flaw was found in Openstack manilla owning a Ceph File system "share", which enables the owner to read/write any manilla share or entire fEPSS 1.3%CVE-2022-23451—An authorization flaw was found in openstack-barbican. The default policy rules for the secret metadata API allowed any authenticated user tEPSS 1.3%CVE-2022-23739CRITICALIncorrect authorization check in GitHub Enterprise Server leading to escalation of privileges in GraphQL API requests from GitHub Apps using scoped user-to-server tokensEPSS 1.3%