Trust of System Event Data

Opis

Security based on event locations are insecure and can be spoofed.

Events are a messaging system which may provide control data to programs listening for events. Events often do not have any type of authentication framework to allow them to be verified from a trusted source. Any application, in Windows, on a given desktop can send a message to any window on the same desktop. There is no authentication framework for these messages. Therefore, any message can be used to manipulate any process on the desktop if the process does not check the validity and safeness of those messages.

Skutki

• Integrity, Confidentiality, Availability, Access Control

  Gain Privileges or Assume Identity; Execute Unauthorized Code or Commands

  If one trusts the system-event information and executes commands based on it, one could potentially take actions based on a spoofed identity.

Zapobieganie

• Architecture and Design

  Never trust or rely any of the information in an Event for security.

Przykłady podatności

• CVE-2004-0213 Attacker uses Shatter attack to bypass GUI-enforced protection for CVE-2003-0908.

Słabość nadrzędna

• CWE-345 Insufficient Verification of Data Authenticity

Słabości podrzędne

• CWE-422 Unprotected Windows Messaging Channel ('Shatter')

Kiedy powstaje

• Architecture and Design
• Implementation

Dotyczy

Not Language-Specific

Źródła

1. The CLASP Application Security Process — Secure Software, Inc., 2005