All Products
Search
Document Center

Security Center:ModifyOperateVul

Last Updated:Feb 20, 2024

Handles detected vulnerabilities. You can fix, check, or ignore the vulnerabilities.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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.
OperationAccess levelResource typeCondition keyAssociated operation
yundun-sas:ModifyOperateVulWrite
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
InfostringYes

The details of the vulnerability. The value of this parameter is in the JSON format and contains the following fields:

  • name: the name of the vulnerability.

  • uuid: the UUID of the server on which the vulnerability is detected.

  • tag: the tag that is added to the vulnerability. Valid values:

    • oval: Linux software vulnerability
    • system: Windows system vulnerability
    • cms: Web-CMS vulnerability
Note You can call the DescribeVulList operation to query the tags that are added to vulnerabilities of other types.
  • isFront: specifies whether a pre-patch is required to fix the Windows system vulnerability. This field is required only for Windows system vulnerabilities. Valid values:

    • 0: no
    • 1: yes
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}]
OperateTypestringYes

The operation that you want to perform on the vulnerability. Valid values:

  • vul_fix: fixes the vulnerability.
  • vul_verify: verifies the vulnerability fix.
  • vul_ignore: ignores the vulnerability.
  • vul_undo_ignore: cancels ignoring the vulnerability.
  • vul_delete: deletes the vulnerability.
vul_fix
TypestringYes

The type of the vulnerability. Valid values:

  • cve: Linux software vulnerability
  • sys: Windows system vulnerability
  • cms: Web-CMS vulnerability
  • emg: urgent vulnerability
  • app: application vulnerability
  • sca: vulnerability that is detected based on software component analysis
Note You cannot fix the urgent vulnerabilities, application vulnerabilities, or vulnerabilities that are detected based on software component analysis.
cve
ReasonstringNo

The reason why the vulnerability is ignored.

Note This parameter is required only when you set OperateType to vul_ignore.
not operate
FromstringNo

The request ID. Set the value to sas.

sas

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The ID of the request, which is used to locate and troubleshoot issues.

DFE4F166-1AC9-4FAC-A4E4-F0608AD705A6

Examples

Sample success responses

JSONformat

{
  "RequestId": "DFE4F166-1AC9-4FAC-A4E4-F0608AD705A6"
}

Error codes

HTTP status codeError codeError messageDescription
400InsufficientAuthorizationCountAuthorization count is insufficient.-
403NoPermissioncaller has no permissionYou are not authorized to do this operation.
500ServerErrorServerError-

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-01-22The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
2023-08-29The Error code has changed. The request parameters of the API has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
Input ParametersThe request parameters of the API has changed.
    Added Input Parameters: From
2023-03-28The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
2022-08-01The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
2022-08-01The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400