18
edits
Security Severity Ratings/Client: Difference between revisions
Jump to navigation
Jump to search
clarify that safe nullptr crashes are often not security issues at all
(clarify that safe nullptr crashes are often not security issues at all) |
|||
| Line 66: | Line 66: | ||
* Identification of users by profiling browsing behavior. | * Identification of users by profiling browsing behavior. | ||
* Corruption of chrome dialogs or user input without the ability to spoof arbitrary messages | * Corruption of chrome dialogs or user input without the ability to spoof arbitrary messages | ||
* Most Denial of Service vulnerabilities, such as triggering a release assertion or those requiring a browser restart | * Most Denial of Service vulnerabilities, such as triggering a release assertion or those requiring a browser restart, when triggerable from the web. In contrast, safe crashes of a content process, like a nullptr deref, are not considered security issues. Neither are safe crashes in the parent which would require a compromised content process. | ||
|} | |} | ||
|} | |} | ||