Service crash via crafted name parameter
Published Oct 9, 2024 · Updated Oct 20, 2024
Buffer overflow in OWASP ModSecurity 3.0.12 allows remote attackers to crash the WAF through a crafted name parameter. The public report does not identify the affected function or unsafe copy operation, and the supplier could not reproduce the behavior. The claimed path requires SecRequestBodyNoFilesLimit far above the recommended 131072-byte setting; only service interruption is reported.
Summary
What happened
Buffer overflow in OWASP ModSecurity 3.0.12 allows remote attackers to crash the WAF through a crafted name parameter. The public report does not identify the affected function or unsafe copy operation, and the supplier could not reproduce the behavior. The claimed path requires SecRequestBodyNoFilesLimit far above the recommended 131072-byte setting; only service interruption is reported.
The record
- CVE
- CVE-2024-46292
- Published
- Oct 9, 2024
- Updated
- Oct 20, 2024
- Vendor
- OWASP ModSecurity
- Product
- ModSecurity
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 9, 2024CVE publishedPublication date reported by the CVE source.
- Oct 20, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo