Open DJ4ddi opened 12 months ago
For now, most of our checks which rely on parameter based analysis, require schema as a prerequisite in order to preform them. For the newer version(which is coming soon), I will add an adaptive way to determine whether or not a check should be preformed on each parameter.
Describe the bug When analyzing an OAS JSON file that has parameters which are missing a schema, the application crashes with the following error:
Example parameter:
To fix the crash, the parameter can be changed as follows:
To Reproduce
cherrybomb --file MyBackend.json --profile passive
.Expected behavior I would expect a warning for this parameter that indicates a missing schema.
Desktop:
Additional context I understand that arbitrarily missing fields aren't necessarily suitable for emitting warnings. However, this particular example was generated by Swagger/Swashbuckle and is reported as valid by other tools.