CSRF protection bypass via incorrect navigation checks
Published Mar 19, 2024 · Updated Feb 13, 2025
CSRF in Apache Wicket 9.1.0 through 9.16.0 and 10.0.0 milestones allows remote attackers to bypass fetch-metadata request checks. FetchMetadataResourceIsolationPolicy incorrectly asserts the HTTP method and fetch-mode conditions used to recognize permitted top-level navigation. Exposure requires an application to use fetch-metadata CSRF protection, and resulting actions remain bounded by the affected application session's permissions.
Summary
What happened
CSRF in Apache Wicket 9.1.0 through 9.16.0 and 10.0.0 milestones allows remote attackers to bypass fetch-metadata request checks. FetchMetadataResourceIsolationPolicy incorrectly asserts the HTTP method and fetch-mode conditions used to recognize permitted top-level navigation. Exposure requires an application to use fetch-metadata CSRF protection, and resulting actions remain bounded by the affected application session's permissions.
The record
- CVE
- CVE-2024-27439
- Published
- Mar 19, 2024
- Updated
- Feb 13, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Wicket
- Classifications
- CWE-352, CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=10.0.0-M1 <10.0.0
- Affected versionversion=9.1.0 <=9.16.0
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