:View and handle Web-CMS vulnerabilities

View the basic information about a vulnerability

1. Log on to the Security Center console.
2. In the left-side navigation pane, choose Precaution > Vulnerabilities.
3. On the Vulnerabilities page, click the Web CMS tab.
4. On the Web CMS tab, view the information about all Web-CMS vulnerabilities detected by Security Center.
   You can perform the following operations on the tab:

   • View vulnerability information
   • View vulnerability priorities

     All Web-CMS vulnerabilities can cause serious damage. This is confirmed by Alibaba Cloud security engineers. Therefore, the priorities of detected Web-CMS vulnerabilities are High and marked in red.

     Note We recommend that you fix Web-CMS vulnerabilities at the earliest opportunity.
   • Handle the vulnerabilities detected by Cloud Firewall

     Security Center uses the Cloud firewall Supports Virtual patches tag to indicate a vulnerability detected by Cloud Firewall. You can click the tag or Protection in the Actions column to go to the Cloud Firewall console to fix the vulnerability. For more information, see Vulnerability prevention.

   • Add a vulnerability to the whitelist

     On the Web CMS tab, you can select the vulnerability you want to add to the whitelist and click Add to Whitelist. After you add a vulnerability to the whitelist, Security Center no longer generates alerts on this vulnerability.

     

     The vulnerability that is added to the whitelist is removed from the vulnerability list on the Web CMS tab. You can click Settings in the upper-right corner of the page to view the vulnerability in the Vul Whitelist section.

     If you want Security Center to detect and generate alerts on a vulnerability that is added to the whitelist, select the vulnerability in the Vul Whitelist section in the Settings panel and click Remove.

     
   • Fix multiple vulnerabilities at a time
     If you fix multiple vulnerabilities at a time, Security Center automatically identifies affected assets and fixes the vulnerabilities on these assets. On the Web CMS tab, you can select the vulnerabilities that you want to fix and click Batch Repair. In the Batch Repair dialog box, view the assets that are affected by the vulnerabilities and click Fix Now.
     Note You can select the vulnerabilities only on the current page. A total of 10, 20, or 50 vulnerabilities can be displayed on each page. Therefore, you can fix a maximum of 50 vulnerabilities at a time.
   • Search for vulnerabilities

     On the Web CMS tab, you can search for vulnerabilities by severity level, asset group, vulnerability status, or vulnerability name. The severity level can be high, medium, or low. The vulnerability status can be handled or unhandled.

     
     Note Fuzzy match is supported for vulnerability search by name.
   • Export vulnerabilities
     On the Web CMS tab, you can click the icon to export and save all detected vulnerabilities to your computer. The vulnerabilities are exported to an Excel file.

     Note The time to export the vulnerabilities varies based on the size of vulnerability data.

Handle vulnerabilities

1. Log on to the Security Center console.
2. In the left-side navigation pane, choose Precaution > Vulnerabilities.
3. On the Vulnerabilities page, click the Web CMS tab.
4. In the Vulnerability column, click the name of the vulnerability that you want to handle, or click Fix in the Actions column of the vulnerability that you want to handle. The panel that shows the vulnerability details appears.
   You can view the details of the vulnerability, number of unhandled vulnerabilities, and information about affected assets.
5. In the panel, view and handle the vulnerability.
   You can perform the following operations:

   • View vulnerability details

     The panel displays all the affected assets and vulnerabilities associated with the vulnerability. You can analyze all the related vulnerabilities and handle multiple vulnerabilities at a time.

     • On the Detail tab, you can view the brief introduction and solution to this vulnerability.
     • On the Pending vulnerability tab, you can view the assets that are affected by this vulnerability.

       You can view the assets affected by the vulnerability and the status of the vulnerability. You can fix or ignore a vulnerability. You can also verify a vulnerability fix or add a vulnerability to the whitelist.

     
     On the Detail tab, click an asset in the Affected Assets column to go to the Vulnerabilities tab of the Assets page. On this tab, view the information about all Web-CMS vulnerabilities associated with this asset.
   • View vulnerability priorities

     All Web-CMS vulnerabilities can cause serious damage. This is confirmed by Alibaba Cloud security engineers. Therefore, the priorities of detected Web-CMS vulnerabilities are High and marked in red.

     
     Note We recommend that you fix Web-CMS vulnerabilities at the earliest opportunity.
   • Search for vulnerabilities

     On the Pending vulnerability tab, you can search for affected assets by vulnerability priority, VPC name, asset group, vulnerability status, server IP address, or server name. The vulnerability priority can be high, medium, or low. The vulnerability status can be handled or unhandled.

     
     Note Fuzzy match is supported for vulnerability search by server IP address or name.
   • View vulnerability status
     • Handled
       • Handled: The vulnerability is fixed.
       • Ignored: The vulnerability is ignored. Security Center no longer generates alerts on this vulnerability.
       • Invalid: The vulnerability cannot be detected. You may have already deleted the file that contains the vulnerability.
     • Unhandled
       • Unfixed: The vulnerability is not fixed.
       • Fixing: The vulnerability is being fixed.
       • Fix Failed: Security Center failed to fix the vulnerability. The file that contains the vulnerability may have been modified or does not exist.
       • Verifying: Security Center is checking whether the vulnerability is fixed.
   • Handle the vulnerabilities of the affected assets

     You can fix or ignore a vulnerability. You can also verify a vulnerability fix or add a vulnerability to the whitelist.

     
     • Fix vulnerabilities
       Click Fix in the Actions column to fix one or more associated vulnerabilities at a time. In the Repair dialog box, click Fix Now.

       Note To prevent service interruptions, we recommend that you back up the data in your system before you fix the vulnerability.
     • Verify: If you fix a vulnerability by using methods rather than Security Center, you must click Verify. After the verification, the status of the vulnerability is updated. If you fix a Web-CMS vulnerability by using Security Center, the fix immediately takes effect. You do not need to verify the fix.
     • Ignore a vulnerability

       Find the vulnerability that you want to ignore, click the icon in the Actions column, and then select Ignore. In the dialog box that appears, enter the description for the ignore operation and click OK. After a vulnerability is ignored, Security Center no longer generates alerts on this vulnerability.

       Search for Handled vulnerabilities, find the vulnerability that is ignored, and then click the vulnerability to go to the panel that shows the vulnerability details. In the panel, move the pointer over the icon in the Status column to view the description of the ignore operation.
       Note The state of this vulnerability changes to Ignored. If you want Security Center to generate alerts on an ignored vulnerability, find the vulnerability in the Handled vulnerability list and click Unignore in the panel.
   • Export affected assets
     On the Pending vulnerability tab, click the icon above the asset list to export and save all affected assets to your computer. The assets are exported to an Excel file.

     Note The time to export the vulnerabilities varies based on the size of asset data.

Web-CMS vulnerabilities that can be detected

References

How often does Security Center detect vulnerabilities?

What are the differences between baselines and vulnerabilities?

What do I do if I cannot enable the vulnerability detection feature for a server on the Assets page?