Numeric array item has no format defined
One or more arrays containing numeric items in your API do not specify the format of the items.
For more details, see the OpenAPI Specification.
The following is an example of how this type of risk could look in your API definition. The array accepts items of the type
integer but their format is not defined:
1parameters: 2 - name: ids 3 in: query 4 description: IDs to filter by 5 required: true 6 type: array 7 items: 8 type: integer 9
Possible exploit scenario
If you do not specify an enforceable format of numeric values, attackers can try to send unexpected input to your backend server. This may cause the backend server to fail in an unexpected way and open the door to further attacks.
For example, the backend server could throw an exception and return a stack trace on the error. The trace could contain information on the exact software stack used in the implementation. This enables the attacker to launch an attack on specific vulnerabilities known in that stack.
Using your internal, company-specific formats is not currently supported.
format parameter for the numeric array items. This ensures that only parameters of the expected format get passed to the backend.
Numeric parameters type
integer can have the format
int64. Numeric parameters type
number can have the format
1parameters: 2 - name: ids 3 in: query 4 description: IDs to filter by 5 required: true 6 type: array 7 items: 8 type: integer 9 format: int32 10
Copyright 42Crunch 2021