QID 580524

QID 580524: Defined Enum Field Values Response Mismatch Schema

In this scenario fields of string type with enum values defined are tested. This test is skipped for all enum fields where values are not defined. All values in the array are used in testing iteratively. The string field is replaced by the defined enum values one at a time and sent to the server. The expectation is that APIs will treat the requests as happy path and the response would match the schema definition for valid response. The response from server for requests with current value being tested does not match the schema definition for valid request.
Based on evaluating response using requests with valid values it is determined that the response code is expected but the response to some valid enum values does not match schema definition for field being tested.

Enforcing handling all the defined enum values in swagger file as happy path will help provide clarity to the API users and avoid abuse of the API by hackers. API users might be confused with the response mismatch to valid values.

CVSS V3 rated as Medium - 5.4 severity.

CVSS V2 rated as Medium - 5 severity.

Solution

Please update the API endpoint response to match the swagger schema definition or update the schema to match the server response.

Vendor References

CVEs related to QID 580524

Software Advisories

Advisory ID	Software	Component	Link

By selecting these links, you may be leaving CVEreport webspace. We have provided these links to other websites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other websites that are more appropriate for your purpose. CVEreport does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, CVEreport does not endorse any commercial products that may be mentioned on these sites. Please address comments about any linked pages to [email protected].