[ThomasTNO]

Adds two new fault categories identified while implementing WFC report support in WuppieFuzz: TNO-S3/WuppieFuzz#397

• HTTP_STATUS_NOT_SPECIFIED (126) – undeclared status code outside the 5xx range (1xx–4xx), mirroring existing 5xx coverage (HTTP_STATUS_500, HTTP_OTHER_STATUS_5XX).
• SECURITY_LDAP_INJECTION (317) – completes the injection category set alongside SQL/XSS/NoSQL/Command injection.

Also synced the json.

[arcuri82]

hi @ThomasTNO. the HTTP_STATUS_NOT_SPECIFIED is technically already handled in SCHEMA_INVALID_RESPONSE. however, maybe it could make sense to have separated categories for wrong status (ie not specified in schema) and wrong bodies (ie not matching structure specified in schema). or maybe just extend the description of SCHEMA_INVALID_RESPONSE with more details and examples.
@ThomasTNO @grebnetiew @Stranger6667 @en-milie what do you think?

[ThomasTNO]

A distinction between the two (status/response code vs response body) would be valuable if you ask me

[arcuri82]

we could remove SCHEMA_INVALID_RESPONSE and introduce two new separated categories: SCHEMA_INVALID_RESPONSE_BODY and SCHEMA_INVALID_RESPONSE_STATUS. how does it sound?

[ThomasTNO]

we could remove SCHEMA_INVALID_RESPONSE and introduce two new separated categories: SCHEMA_INVALID_RESPONSE_BODY and SCHEMA_INVALID_RESPONSE_STATUS. how does it sound?

I would like that

[arcuri82]

@ThomasTNO you can remove HTTP_STATUS_NOT_SPECIFIED from this PR. then, if @Stranger6667 and @en-milie agree on replacing SCHEMA_INVALID_RESPONSE, I can do it on a separated PR

[arcuri82]

thx. i will need to write some documentation to explain all steps needed when adding a new code. for example, constraints under src/main/resources/wfc/schemas/report.yaml needs to be updated for FaultCategoryId, as well as need to update release_notes.md

[ThomasTNO]

@arcuri82 please tag me as soon as the other PR is present. I can then directly incorporate it in our WIP PR on enabling WFC report in WuppieFuzz. Ideally I would prefer a new release as well so that versioning of the standard stays aligned.