Difference between revisions of "Security Levels"
(→Security Levels) |
|||
| Line 1: | Line 1: | ||
= Security Levels = | = Security Levels = | ||
| + | |||
'''This document explains how we classify security issues that are discovered in our product.''' | '''This document explains how we classify security issues that are discovered in our product.''' | ||
| − | == Critical == | + | |
| − | + | === Critical === | |
| − | + | ||
| − | + | A critical rating applies to vulnerabilities that allow remote, unauthenticated access and code execution, | |
| − | == Important == | + | with no user interaction required. These would allow complete system compromise and can easily be |
| − | + | exploited by automated scripts such as worms. | |
| − | + | ||
| − | + | === Important === | |
| − | + | ||
| − | == Moderate == | + | An important rating applies to vulnerabilities that allow system authentication levels to be compromised. |
| − | + | These include allowing local users to elevate their privilege levels, unauthenticated remote users to see | |
| − | + | resources that should require authentication to view, the execution of arbitrary code by remote users, | |
| − | + | or any local or remote attack that could result in an denial of service. | |
| − | == Trivial == | + | |
| − | + | === Moderate === | |
| − | + | ||
| − | + | A moderate rating applies to vulnerabilities that rely on unlikely scenarios in order to compromise the system. | |
| − | + | These usually require that a flawed or unlikely configuration of the system be in place, and only occur | |
| + | in rare situations. | ||
| + | |||
| + | === Trivial === | ||
| + | |||
| + | A trivial rating applies to vulnerabilities that do not fit into the higher categories. These vulnerabilities | ||
| + | occur in very unlikely situations and configurations, often requiring extremely tight timing of execution | ||
| + | and/or for events to occur that are out of the attacker's control. This rating may also be given to | ||
| + | vulnerabilities that, even if successful, impose few or no consequences on the system. | ||
| + | |||
| + | Security Advisory Notices can be viewed @ http://blog.whmcs.com/security.php | ||
| + | |||
| + | __NOTOC__ | ||
Revision as of 07:49, 10 April 2013
Security Levels
This document explains how we classify security issues that are discovered in our product.
Critical
A critical rating applies to vulnerabilities that allow remote, unauthenticated access and code execution, with no user interaction required. These would allow complete system compromise and can easily be exploited by automated scripts such as worms.
Important
An important rating applies to vulnerabilities that allow system authentication levels to be compromised. These include allowing local users to elevate their privilege levels, unauthenticated remote users to see resources that should require authentication to view, the execution of arbitrary code by remote users, or any local or remote attack that could result in an denial of service.
Moderate
A moderate rating applies to vulnerabilities that rely on unlikely scenarios in order to compromise the system. These usually require that a flawed or unlikely configuration of the system be in place, and only occur in rare situations.
Trivial
A trivial rating applies to vulnerabilities that do not fit into the higher categories. These vulnerabilities occur in very unlikely situations and configurations, often requiring extremely tight timing of execution and/or for events to occur that are out of the attacker's control. This rating may also be given to vulnerabilities that, even if successful, impose few or no consequences on the system.
Security Advisory Notices can be viewed @ http://blog.whmcs.com/security.php