Security Severity Ratings/Client: Difference between revisions

|csectype-clickjacking || client security issues due to techniques that cause a user to unintentionally click or tap on a browser control, either by obscuring the true target of the click or by causing the target to appear by surprise in place of the item the user intended to click or tap

|csectype-disclosure || client issues that cause disclosure of sensitive user data or personal information (see also csectype-side-channel and csectype-sop)

|csectype-framepoisoning || client crashes caused by dereferencing a poisoned (deleted) nsIFrame object (presumed to be limited to a Denial of Service)

|csectype-nullptr || client crashes due to a guaranteed null dereference (do not use for near-null crashes with a content-controlled offset)

|csectype-oom || client crashes or hangs that occurs in Out Of Memory conditions

|csectype-race || client security issues due to a race condition

|csectype-sandbox-escape || client security issues where a low-privilege process can cause memory corruption or arbitrary code execution in a higher-privilege processs (for example, through malformed IPC messages or Shared Memory)

|csectype-side-channel || Disclosure of sensitive information or state through side-effects (typically, timing)

|csectype-sop || violations of the client Same Origin Policy including Universal-XSS (see also csectype-side-channel for less severe "leaks")

|csectype-spoof || client security issues due to UI Redress attacks or manipulation of the browser UI to fool users into taking the wrong action (excluding csectype-clickjacking issues)

|csectype-undefined || client security issues—or potential issues—due to undefined compiler behavior