owasp-integer-limit-legacy
This rule was removed in v0.7.0 of vacuum.
Integers should be limited to mitigate resource exhaustion attacks. Ensure that minimum
and maximum
have been defined.
This rule does not check for 3.1 exclusiveMinimum
and exclusiveMaximum
properties.
JSONPath used
$..[?(@.type)]
Bad example
openapi: "3.1.0"
info:
version: "1.0"
components:
schemas:
Foo:
type: integer
Good Example
openapi: "3.1.0"
info:
version: "1.0"
components:
schemas:
Foo:
type: integer
maximum: 99
minimum: 1
How do I fix this violation?
Ensure that minimum
and maximum
have been specified on integer values.