Fallos del tipo CWE-276

953 resultados

Permissões padrão incorretas

Ocorre quando um software cria arquivos, diretórios ou recursos com permissões padrão muito permissivas, expondo dados sensíveis a usuários não autorizados do sistema. O risco é que qualquer outro processo ou usuário consegue ler, modificar ou deletar informações que deveriam ser privadas.

Ejemplo

Um aplicativo cria um arquivo de configuração com senha de banco de dados com permissões 0644 (legível por qualquer usuário), em vez de 0600 (só o dono). Outro usuário no mesmo servidor consegue ler esse arquivo e obtém as credenciais.

Cómo mitigar

Defina permissões explícitas e restritivas no ato da criação (use umask apropriado, chmod, ou APIs de segurança). Sempre revise e documente quais permissões cada recurso deve ter, testando a realidade no sistema de arquivos ou controle de acesso após o deploy.

CVE-2025-31655MEDIUMIncorrect default permissions for some Intel(R) Battery Life Diagnostic Tool within Ring 3: User Applications may allow an escalation of priEPSS 0.1%CVE-2023-40132HIGHIn setActualDefaultRingtoneUri of RingtoneManager.java, there is a possible way to bypass content providers read permissions due to a missinEPSS 0.1%CVE-2023-21139—In bindPlayer of MediaControlPanel.java, there is a possible launch arbitrary activity in SysUI due to Unsafe Intent. This could lead to locEPSS 0.1%CVE-2023-21138—In onNullBinding of CallRedirectionProcessor.java, there is a possible long lived connection due to improper input validation. This could leEPSS 0.1%CVE-2023-21121—In onResume of AppManagementFragment.java, there is a possible way to prevent users from forgetting a previously connected VPN due to impropEPSS 0.1%CVE-2026-20718MEDIUMIncorrect default permissions for some Intel(R) NPU Driver software installers before version 32.0.100.4511 within Ring 3: User ApplicationsEPSS 0.1%CVE-2018-9369HIGHIn bootloader there is fastboot command allowing user specified kernel command line arguments. This could lead to local escalation of privilEPSS 0.1%CVE-2023-21104MEDIUMIn applySyncTransaction of WindowOrganizer.java, a missing permission check could lead to local information disclosure with no additional exEPSS 0.1%CVE-2018-9431HIGHIn OSUInfo of OSUInfo.java, there is a possible escalation of privilege due to improper input validation. This could lead to local escalatioEPSS 0.1%CVE-2024-43769HIGHIn isPackageDeviceAdmin of PackageManagerService.java, there is a possible edge case which could prevent the uninstallation of CloudDpc due EPSS 0.1%CVE-2024-40654HIGHIn multiple locations, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege withEPSS 0.1%CVE-2024-40655HIGHIn bindAndGetCallIdentification of CallScreeningServiceHelper.java, there is a possible way to maintain a while-in-use permission in the bacEPSS 0.1%CVE-2024-47012HIGHIn mm_GetMobileIdIndexForNsUpdate of mm_GmmPduCodec.c, there is a possible out of bounds write due to an incorrect bounds check. This could EPSS 0.1%CVE-2024-34730HIGHIn multiple locations, there is a possible bypass of user consent to enabling new Bluetooth HIDs due to a logic error in the code. This coulEPSS 0.1%CVE-2024-49737HIGHIn applyTaskFragmentOperation of WindowOrganizerController.java, there is a possible way to launch arbitrary activities as the system UID duEPSS 0.1%CVE-2024-53835HIGHthere is a possible biometric bypass due to an unusual root cause. This could lead to local escalation of privilege with no additional execuEPSS 0.1%CVE-2018-9432HIGHIn createPhonebookDialogView and createMapDialogView of BluetoothPermissionActivity.java, there is a possible permissions bypass. This couldEPSS 0.1%CVE-2024-11624HIGHthere is a possible to add apps to bypass VPN due to Undeclared Permission . This could lead to local escalation of privilege with no additiEPSS 0.1%CVE-2024-53840HIGHthere is a possible biometric bypass due to an unusual root cause. This could lead to local escalation of privilege with no additional execuEPSS 0.1%CVE-2024-49744HIGHIn checkKeyIntentParceledCorrectly of AccountManagerService.java, there is a possible way to bypass parcel mismatch mitigation due to unsaEPSS 0.1%