Handles detected vulnerabilities. You can fix, check, or ignore the vulnerabilities.
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 Resourcesis 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:ModifyOperateVul | update |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| Info | string | Yes | The details of the vulnerability. The value of this parameter is in the JSON format and contains the following fields:
Note
You can call the DescribeVulList operation to query the tags that are added to vulnerabilities of other types.
Note
You can fix multiple vulnerabilities at a time. Separate the details of multiple vulnerabilities with commas (,). You can call the DescribeVulLIst operation to query the details of vulnerabilities.
| [{"name":"alilinux2:2.1903:ALINUX2-SA-2022:0007","uuid":"a3bb82a8-a3bd-4546-acce-45ac34af****","tag":"oval","isFront":0},{"name":"alilinux2:2.1903:ALINUX2-SA-2022:0007","uuid":"98a6fecc-88cd-46f2-8e35-f808a388****","tag":"oval","isFront":0}] |
| OperateType | string | Yes | The operation that you want to perform on the vulnerability. Valid values:
| vul_fix |
| Type | string | Yes | The type of the vulnerability. Valid values:
Note
You cannot fix the urgent vulnerabilities, application vulnerabilities, or vulnerabilities that are detected based on software component analysis.
| cve |
| Reason | string | No | The reason why the vulnerability is ignored. Note
This parameter is required only when you set OperateType to vul_ignore.
| not operate |
| From | string | No | The request ID. Set the value to sas. | sas |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "DFE4F166-1AC9-4FAC-A4E4-F0608AD705A6"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | InsufficientAuthorizationCount | Authorization count is insufficient. | - |
| 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-01-22 | The Error code has changed | View Change Details |
| 2023-08-29 | The Error code has changed. The request parameters of the API has changed | View Change Details |
| 2023-03-28 | The Error code has changed | View Change Details |
| 2022-08-01 | The Error code has changed | View Change Details |
| 2022-08-01 | The Error code has changed | View Change Details |