As of December 31st, 2023 ThreadFix 2.X has reached End of Life and is no longer supported. For any further information please contact the Success and Implementation team.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

/rest/{version}/vulnerabilities/{vulnerabilityId}/setContested

Descriptor

Value

HTTP Method

POST

Description

Update the specified vulnerability's Contested status

Required Permission

Update Vulnerability Contested Status

Version Introduced2.7.2
Changes in 2.7.9Added a parameter 'contested' to control if you set the Contested status to True or False.


Request Header Parameters

Parameter

Value

Required

Description

Accept

String

Yes

A value of ‘application/json’ must be provided.

Request POST Data Parameters

Parameter

Value

Required

Description

contested

Boolean

No

Provide 'true' to mark the vulnerability as Contested.  Provide 'false' to mark the vulnerability as Not Contested.

Defaults to 'true' if not provided.

Sample Calls: 


curl --insecure -H 'Accept: application/json' -H "Authorization: APIKEY {apiKey}" -X POST --data 'contested=true' http://localhost:8080/threadfix/rest/latest/vulnerabilities/{vulnerabilityId}/setContested


Sample Output:


{
    "message": "The vulnerability has been successfully set as contested.",
    "success": true,
    "responseCode": -1,
    "object": 241
}
  • No labels