-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Possible representation bug in uploads part of JSON audit log format #1173
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
Comments
Linking this issue with #1174, as they seems to be on the same piece of code. |
Not the same issue as #1174, but looks like an easy fix. |
Thanks @p0pr0ck5 ;) |
Thank you guys. |
Each uploaded file is a separate yajl array, but we forgot to open the a map for the proper k/v pairs. This fixes issue owasp-modsecurity#1173.
@dune73 can you try the fix in p0pr0ck5@e54b150? I won't have time to test for a bit but this should resolve the issue, small oversight on my part. We don't log file upload data so I wasn't as thorough as I should have been. |
^ Once this is tested I'll submit the PR |
Looks good here:
Thank you for the quick fix. |
Each uploaded file is a separate yajl array, but we forgot to open the a map for the proper k/v pairs. This fixes issue #1173.
Pull request #1181 was merged! thanks! |
Each uploaded file is a separate yajl array, but we forgot to open the a map for the proper k/v pairs. This fixes issue owasp-modsecurity#1173.
Each uploaded file is a separate yajl array, but we forgot to open the a map for the proper k/v pairs. This fixes issue owasp-modsecurity#1173.
I have the following entry in the JSON audit log format:
Within the info tag, there is a list of items and not a list of key-value pairs as would be expected. It might have to do with the way the data is represented within ModSecurity (-> corresponding native audit log format part "J" is a CSV), but this seems to be a bug to me.
The text was updated successfully, but these errors were encountered: