-
Notifications
You must be signed in to change notification settings - Fork 1.7k
chore: prepare v2.9.9 #3389
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
Merged
Merged
chore: prepare v2.9.9 #3389
Conversation
This file contains hidden or 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
theseion
requested changes
May 21, 2025
Co-authored-by: Max Leske <250711+theseion@users.noreply.github.com>
|
theseion
approved these changes
May 21, 2025
arnout
pushed a commit
to buildroot/buildroot
that referenced
this pull request
Jun 30, 2025
Fixes the following security issues: - CVE 2025-47947: Versions up to and including 2.9.8 are vulnerable to denial of service in one special case (in stable released versions): when the payload's content type is application/json, and there is at least one rule which does a sanitiseMatchedBytes action. A patch is available at pull request 3389 and expected to be part of version 2.9.9. No known workarounds are available. For more information, see: - https://nvd.nist.gov/vuln/detail/CVE-2025-47947 - owasp-modsecurity/ModSecurity#3389 - CVE-2025-48866: Versions prior to 2.9.10 contain a denial of service vulnerability similar to GHSA-859r-vvv8-rm8r/CVE-2025-47947. The `sanitiseArg` (and `sanitizeArg` - this is the same action but an alias) is vulnerable to adding an excessive number of arguments, thereby leading to denial of service. Version 2.9.10 fixes the issue. As a workaround, avoid using rules that contain the `sanitiseArg` (or `sanitizeArg`) action. For more information, see: - https://nvd.nist.gov/vuln/detail/CVE-2025-48866 - owasp-modsecurity/ModSecurity@3a54cce For more details on the version bump, see: - https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.8 - https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.9 - https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.10 Also this patch change the _SOURCE variable that now include a 'v' prefixing the version. Signed-off-by: Thomas Perale <thomas.perale@mind.be> [Julien: update hash source url in hash file comment] Signed-off-by: Julien Olivain <ju.o@free.fr>
arnout
pushed a commit
to buildroot/buildroot
that referenced
this pull request
Jul 11, 2025
Fixes the following security issues: - CVE 2025-47947: Versions up to and including 2.9.8 are vulnerable to denial of service in one special case (in stable released versions): when the payload's content type is application/json, and there is at least one rule which does a sanitiseMatchedBytes action. A patch is available at pull request 3389 and expected to be part of version 2.9.9. No known workarounds are available. For more information, see: - https://nvd.nist.gov/vuln/detail/CVE-2025-47947 - owasp-modsecurity/ModSecurity#3389 - CVE-2025-48866: Versions prior to 2.9.10 contain a denial of service vulnerability similar to GHSA-859r-vvv8-rm8r/CVE-2025-47947. The `sanitiseArg` (and `sanitizeArg` - this is the same action but an alias) is vulnerable to adding an excessive number of arguments, thereby leading to denial of service. Version 2.9.10 fixes the issue. As a workaround, avoid using rules that contain the `sanitiseArg` (or `sanitizeArg`) action. For more information, see: - https://nvd.nist.gov/vuln/detail/CVE-2025-48866 - owasp-modsecurity/ModSecurity@3a54cce For more details on the version bump, see: - https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.8 - https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.9 - https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.10 Also this patch change the _SOURCE variable that now include a 'v' prefixing the version. Signed-off-by: Thomas Perale <thomas.perale@mind.be> [Julien: update hash source url in hash file comment] Signed-off-by: Julien Olivain <ju.o@free.fr> (cherry picked from commit 3d593a8) Signed-off-by: Thomas Perale <thomas.perale@mind.be>
arnout
pushed a commit
to buildroot/buildroot
that referenced
this pull request
Jul 11, 2025
Fixes the following security issues: - CVE 2025-47947: Versions up to and including 2.9.8 are vulnerable to denial of service in one special case (in stable released versions): when the payload's content type is application/json, and there is at least one rule which does a sanitiseMatchedBytes action. A patch is available at pull request 3389 and expected to be part of version 2.9.9. No known workarounds are available. For more information, see: - https://nvd.nist.gov/vuln/detail/CVE-2025-47947 - owasp-modsecurity/ModSecurity#3389 - CVE-2025-48866: Versions prior to 2.9.10 contain a denial of service vulnerability similar to GHSA-859r-vvv8-rm8r/CVE-2025-47947. The `sanitiseArg` (and `sanitizeArg` - this is the same action but an alias) is vulnerable to adding an excessive number of arguments, thereby leading to denial of service. Version 2.9.10 fixes the issue. As a workaround, avoid using rules that contain the `sanitiseArg` (or `sanitizeArg`) action. For more information, see: - https://nvd.nist.gov/vuln/detail/CVE-2025-48866 - owasp-modsecurity/ModSecurity@3a54cce For more details on the version bump, see: - https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.8 - https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.9 - https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.10 Also this patch change the _SOURCE variable that now include a 'v' prefixing the version. Signed-off-by: Thomas Perale <thomas.perale@mind.be> [Julien: update hash source url in hash file comment] Signed-off-by: Julien Olivain <ju.o@free.fr> (cherry picked from commit 3d593a8) Signed-off-by: Thomas Perale <thomas.perale@mind.be>
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
This PR prepares new release of mod_security2: 2.9.9
why
The source tree has several modifications and a critical bug fix.
See CVE-2025-47947.