CWE-360: Trust of System Event Data
2 CVEs have CWE-360 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 0.501%.
Security based on event locations are insecure and can be spoofed.
Events are a messaging system that 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.
Child of CWE-345: Insufficient Verification of Data Authenticity
Mitigations
- Architecture and Design: Never trust or rely on any of the information in an Event for security.
Observed examples
- CVE-2004-0213: Attacker uses Shatter attack to bypass GUI-enforced protection for CVE-2003-0908.
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-360'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-360'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).