Update to libddwaf 1.5.1 #2306
Merged
Update to libddwaf 1.5.1 #2306
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Also update vendored rulesets to 1.4.1 Notable libddwaf API changes include: - ability to set sideband rule data - ability to toggle rules - proper separation of return code vs decided action - ability to hint at multiple actions - non-reliance on garbage collector (finalization must be explicit)
While the presence of a ruby-platform gem for these should be picked up by bundler, sometimes it is not. Also, this makes it a bit more future-proof, so that bundler doesn't attempt to pick a version that has no ruby platform gem, and then proceed to fail.
While the presence of a ruby-platform gem for these should be picked up by bundler, sometimes it is not. Also, this makes it a bit more future-proof, so that bundler doesn't attempt to pick a version that has no ruby platform gem, and then proceed to fail.
Some AppSec spec examples have to be tested against rack-contrib
Previoulsy setting the tag would work but the change would be silently dropped, resulting in the change being absent from the final trace.
Prevents accumulation of instrumentation middlewares if multiple configure blocks are being called, like over app hot-reloading (e.g Rails development mode, which rereads initializers) or across a sequence of examples within a spec suite. Since watchers are essentially static, they need only to be set up once per process, ever.
Rack and Rails are lazily populating upon access. Depending on the access pattern this may mean that body data would not be available to AppSec for analysis. This is worked around by a call to the side-effectful accessors.
Consequently, context will not be set in Rack env, trickling down to either disablement or enablement of other instrumented calls, consistently for the whole request.
This would apply to handle as well, yet currently handle is a value that exists only once per application, so is never to be freed since there is no place for its finalize to be called.
This covers the following AppSec integrations: - Rack - Rails - Sinatra
3a21a7e to
35f67c4
Compare
e2eb1b2 to
08d9b11
Compare
JSONBodyParser replaces PostBodyContentTypeParser
With POST requests, a CSRF token is theoretically needed, but we have none. Skip the filter, using the appropriate method depending on Rails versions. Also the mock app may not have the filter defined.
Prior to 0.7 an argument is lacking to generate multipart requests without uploading a file.
ca7e22e to
397ec9a
Compare
ivoanjo
approved these changes
Oct 13, 2022
This reverts commit ba1ef94.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Update libddwaf to 1.5.1
Motivation
Support for new features, some fixes, and performance improvements.
How to test the change?
There should be specs + system tests covering these.