Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make multipart/mixed an OWASP-allowed content type #2002

Open
HeikoTheissen opened this issue Sep 26, 2024 · 2 comments · May be fixed by coreruleset/coreruleset#3858
Open

Make multipart/mixed an OWASP-allowed content type #2002

HeikoTheissen opened this issue Sep 26, 2024 · 2 comments · May be fixed by coreruleset/coreruleset#3858
Assignees

Comments

@HeikoTheissen
Copy link
Contributor

HeikoTheissen commented Sep 26, 2024

OWASP maintains a set of core rules which, among others, contains a list of "allowed content types for requests"

https://github.com/coreruleset/coreruleset/blob/a2f477d9d3171ac23cde3a3fc719356bc3db55db/rules/REQUEST-901-INITIALIZATION.conf#L200

which is then used in another rule

https://github.com/coreruleset/coreruleset/blob/a2f477d9d3171ac23cde3a3fc719356bc3db55db/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf#L1013.

This list is not set in stone, for example, multipart/related was added as a result of coreruleset/coreruleset#1721.

To support OData multipart $batch requests, should the OData TC raise another issue to have multipart/mixed included?

@ralfhandl
Copy link
Contributor

@HeikoTheissen to approach OWASP

@HeikoTheissen
Copy link
Contributor Author

@HeikoTheissen to approach OWASP

@mikepizzo offered to ask a colleague at Microsoft, I'd like to await his response first so that I can better judge what impact the rule 901162 (which we want modified) actually has.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Review
Development

Successfully merging a pull request may close this issue.

2 participants