CWE-279 · Słabość
Incorrect Execution-Assigned Permissions
- Abstrakcja
- Wariant
- Status
- Szkic
- Dodano
- 19 lipca 2006
- Ostatnia zmiana
- 11 grudnia 2025
Opis
While it is executing, the product sets the permissions of an object in a way that violates the intended permissions that have been specified by the user.
Skutki
Confidentiality, Integrity
Read Application Data; Modify Application Data
Zapobieganie
Architecture and Design, Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Przykłady podatności
- CVE-2002-0265 Log files opened read/write.
- CVE-2003-0876 Log files opened read/write.
- CVE-2002-1694 Log files opened read/write.
Słabość nadrzędna
Kiedy powstaje
- Implementation — REALIZATION: This weakness is caused during implementation of an architectural security tactic.
- Architecture and Design
- Operation
Dotyczy
Not Language-Specific
Wpis z katalogu CWE 4.20.