Help Center/ Host Security Service/ API Reference/ API Description/ Security Operations/ Viewing Vulnerability Handling History
Updated on 2026-04-03 GMT+08:00
View PDF
Share

Viewing Vulnerability Handling History

Function

This API is used to query vulnerability handling history.

Authorization Information

Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.

  • If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
  • If you are using identity policy-based authorization, no identity policy-based permission required for calling this API.

URI

GET /v5/{project_id}/vulnerability/handle-history

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID
Table 2 Query Parameters

Parameter

Mandatory

Type

Description

enterprise_project_id

Yes

String

Enterprise project ID

status

No

Array of strings

Vulnerability status. The options are as follows:

  • vul_status_unfix: not fixed

  • vul_status_ignored: ignored

  • vul_status_verified: verification in progress

  • vul_status_fixing: fixing

  • vul_status_fixed: fixed

  • vul_status_reboot: fixed and pending restart

  • vul_status_failed: fix failed

  • vul_status_fix_after_reboot: Restart the server and try again.

vul_id

No

String

Vulnerability ID.

vul_type

No

String

Vulnerability type. The options are as follows:

  • linux_vul: Linux vulnerabilities

  • windows_vul: Windows vulnerabilities

  • web_cms: Web-CMS vulnerabilities

  • app_vul: application vulnerabilities

  • urgent_vul: emergency vulnerabilities

asset_value

No

String

Asset importance. The options are as follows:

  • important

  • common

  • test

group_name

No

String

Server group

host_name

No

String

Server name

host_ip

No

String

Server IP address

cluster_id

No

String

Cluster ID

sort_key

No

String

Sorting fields. The options are as follows:

  • handle_time: handling time

sort_dir

No

String

Sorting order. If sort_key is set, the returned results are sorted in ascending the order specified by sort_key. The default order is descending. The options are as follows:

  • asc: ascending order

  • desc: descending order

public_ip

No

String

Server EIP

private_ip

No

String

Server private IP address

limit

Yes

Integer

Number of records on each page.

offset

Yes

Integer

Offset.

Request Parameters

Table 3 Request header parameters

Parameter

Mandatory

Type

Description

X-Auth-Token

Yes

String

Definition

User token, which contains user identity and permissions. The token can be used for identity authentication when an API is called. For details about how to obtain the token, see Obtaining a User Token.

Constraints

N/A

Range

The value can contain 1 to 32,768 characters.

Default Value

N/A

Response Parameters

Status code: 200

Table 4 Response body parameters

Parameter

Type

Description

data_list

Array of data_list objects

Details

total_num

Integer

Total
Table 5 data_list

Parameter

Type

Description

id

String

Unique ID of history

user_name

String

Username

type

String

Vulnerability type

host_id

String

Server ID

host_name

String

Server name

public_ip

String

Server EIP

private_ip

String

Server private IP address.

handle_time

String

Handling time

status

String

Handling status

failed_reason

String

Failure cause

description

String

Remarks

vul_id

String

Vulnerability ID.

vul_name

String

Vulnerability name

asset_value

String

Asset importance

cve_list

Array of VulCveInfo objects

CVE list

app_name

String

Software name

app_path

String

Application software path

app_version

String

Software version

handle_type

String

Handling type

cluster_id

String

Cluster ID

container_name

String

Container Name

container_id

String

Container ID
Table 6 VulCveInfo

Parameter

Type

Description

cve_id

String

cve ID

cvss

Float

CVE score

vul_id

String

Vulnerability ID.

Example Requests

None

Example Responses

Status code: 200

Request succeeded.

{
  "total_num" : 41496,
  "data_list" : [ {
    "id" : "d6f***20-1d03-4692-b8a5-9795****188e",
    "user_name" : "scc_hss_g0*******8_01",
    "type" : "linux_vul",
    "host_id" : "29****064-edfc-4f45-9fe4-0ee****740c9",
    "host_name" : "ecs-HSStest-600****51",
    "public_ip" : "",
    "private_ip" : "192.168.0.**",
    "handle_time" : "1737424707845",
    "status" : "vul_status_ignored",
    "description" : "875 Linux vulnerabilities are added to the whitelist.",
    "vul_id" : "EulerOS-SA-2024-1583",
    "vul_name" : "EulerOS-SA-2024-1583 bind security update",
    "asset_value" : "common",
    "cve_list" : [ {
      "cvss" : 0,
      "cve_id" : "CVE-2023-50387"
    }, {
      "cvss" : 0,
      "cve_id" : "CVE-2023-50868"
    } ],
    "app_name" : "python3-bind",
    "app_version" : "9.11.21-4.h15.eulerosv2r10",
    "handle_type" : "add_to_whitelist"
  } ]
}

Status Codes

Status Code

Description

200

Request succeeded.

Error Codes

See Error Codes.

Parent Topic: Security Operations