QID 580506

QID 580506: Decimal Fields Maximum Limit Response Mismatch Schema

In this scenario maximum value for decimal fields are tested. Values more than the maximum defined in the swagger file for decimal fields are sent to the server for the endpoint being tested. The expectation is that APIs will reject the request as invalid, if the value is more than it's maximum. Based on testing done using requests with values more than the maximum it is determined that the maximum limits defined in the swagger file are enforced but not as expected. The request with invalid values is rejected. The response code received for the request with higher values for decimal fields is expected but the response does not match the response documented in the swagger file schema.

Enforcing the maximum value defined on the decimal field swagger file will help provide clarity to the API users and avoid abuse of the API by hackers. Enforcing limits help in mitigating resource exhaustion attacks. Since enforcing maximum limit 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 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 580506

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