QID 580521

QID 580521: Enum Fields Response Mismatch Schema Definition

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. Values that are not part of the defined enum values are sent to the server for the endpoint being tested.The expectation is that server will reject the request as invalid, instead of accepting the undefined value or defaulting to a defined enum value. The response from server for requests with value not defined in swagger file should match the schema definition for invalid request.
Based on the response using requests with invalid values it is determined that the request with invalid value is rejected. The response code to unexpected values in enum fields is expected but response does not match schema definition for field being tested.

Enforcing defined values and responses in swagger file for enum fields will help provide clarity to the API users and avoid abuse of the API by hackers. Since handling enum field types is not adhering to the schema, the current end point is potential to resource exhaustion attacks.

CVSS V3 rated as High - 6.3 severity.

CVSS V2 rated as Medium - 5 severity.

Solution

Please ensure that the server rejects invalid requests with documented error code and schemas. Add input validations and ensure the server implementation is aligned with swagger file.

Vendor References

CVEs related to QID 580521

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].