Privilege escalation via reusable non-user-specific CSRF salts
Published Oct 14, 2024 · Updated Nov 1, 2024
Cross-site request forgery in Apache Roller before 6.1.4 allows remote authenticated users to escalate privileges on multi-user sites. Roller's request-token scheme did not bind salts to individual users or make them single-use, allowing trusted weblog content to trigger privileged actions. The attack requires a multi-blog/user installation that permits weblog owners to publish arbitrary content; Apache has not disclosed the resulting privileged actions.
Summary
What happened
Cross-site request forgery in Apache Roller before 6.1.4 allows remote authenticated users to escalate privileges on multi-user sites. Roller's request-token scheme did not bind salts to individual users or make them single-use, allowing trusted weblog content to trigger privileged actions. The attack requires a multi-blog/user installation that permits weblog owners to publish arbitrary content; Apache has not disclosed the resulting privileged actions.
The record
- CVE
- CVE-2024-46911
- Published
- Oct 14, 2024
- Updated
- Nov 1, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Roller
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 14, 2024CVE publishedPublication date reported by the CVE source.
- Nov 1, 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=1.0.0 <6.1.4
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