Queries a list of assets that support fixing based on vulnerability names.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
yundun-sas:DescribeUuidsByVulNames | get | *All Resources * |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
Lang | string | No | The language of the content within the request and response. Default value: zh. Valid values:
| zh |
Type | string | Yes | The type of the vulnerability. Valid values:
| cve |
StatusList | string | No | The status of the vulnerability. Separate multiple states with commas (,). Valid values:
| 1,4 |
Tag | string | No | The tag of the vulnerability. | oval |
Level | string | No | The severity of the vulnerability. Separate multiple severities with commas (,). Valid values:
| high,low |
Dealed | string | No | Specifies whether the vulnerability is fixed. Valid values:
| n |
GroupId | long | No | The ID of the asset group. | 11286014 |
VpcInstanceIds | string | No | The ID of the virtual private cloud (VPC) in which the vulnerability is detected. Separate multiple IDs with commas (,). | vpc-uf6ssrvbrwe37ekw****,vpc-bp1aevy8sofi8mh1q**** |
Remark | string | No | The remarks for the asset affected by the vulnerability. The value can be the private IP address, public IP address, or name of the asset. Fuzzy match is supported. | 10.7. |
SearchTags | string | No | The tags that are used to search for the vulnerability. | oval |
FieldName | string | No | The name of the search field that is used to query containers. | namespace |
FieldValue | string | No | The value of the search field that is used to query containers. | cas-adad-qeqwe |
TargetType | string | No | The type of the query condition. Valid values:
| uuid |
Necessity | string | No | The priority based on which the vulnerability is fixed. Separate multiple priorities with commas (,). Valid values:
| asap,later,nntf |
VulNames | array | Yes | An array that consists of the names of vulnerabilities. Note
You can call the DescribeGroupedVul operation to obtain the names of vulnerabilities.
| |
string | Yes | The name of the vulnerability. | centos:8:rhsa-2020:1665 |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "97286A-4A6B-4A4-95FA-EC7E3E2451",
"MachineInfoStatistics": [
{
"Uuid": "18375c64-eaa2-4702-92b0-4ee7******",
"MachineIp": "192.168.XX.XX",
"Os": "windows",
"MachineName": "TestMachine",
"MachineInstanceId": "i-wz9gd1os5talju****",
"RegionId": "cn-hangzhou",
"InternetIp": "47.98.XX.XX",
"IntranetIp": "172.18.XX.XX"
}
],
"VulCount": 2
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
403 | NoPermission | caller has no permission | You are not authorized to do this operation. |
500 | ServerError | ServerError | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-06-11 | The response structure of the API has changed | View Change Details |
2023-07-06 | The response structure of the API has changed | View Change Details |