QID 580527

QID 580527: String Fields Exact Maximum Length Response Mismatch Schema

In this scenario fields of string type are updated with strings of exact maximum length as defined in the swagger file. If the maximum length is not defined for the string type this test is skipped. All string fields with a maximum length defined are updated iteratively and sent to the server. The expectation is that server will treat the requests as happy paths since the length of inserted strings matches the maximum. The purpose of the test is to verify that all defined boundaries are properly implemented. Based on the response using requests with valid values it is determined that valid values are accepted. The response code to valid value matches swagger definition. The response to some valid values does not match schema definition for field being tested.

Enforcing maximum string length defined in swagger file 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.3 severity.

CVSS V2 rated as High - 7.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 580527

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