Forced searches via missing CSRF token
Published Jan 5, 2023 · Updated Nov 25, 2024
CSRF in the Search component of OpenACS Bug Tracker allows remote attackers to force authenticated users to submit crafted search requests. The lib/nav-bar.adp Search form omitted the CSRF token later added by the upstream patch, leaving requests without a verified intent signal. Exploitation requires an authenticated user to follow attacker-controlled content; published evidence identifies no consequence beyond an unwanted search request.
Summary
What happened
CSRF in the Search component of OpenACS Bug Tracker allows remote attackers to force authenticated users to submit crafted search requests. The lib/nav-bar.adp Search form omitted the CSRF token later added by the upstream patch, leaving requests without a verified intent signal. Exploitation requires an authenticated user to follow attacker-controlled content; published evidence identifies no consequence beyond an unwanted search request.
The record
- CVE
- CVE-2016-15009
- Published
- Jan 5, 2023
- Updated
- Nov 25, 2024
- Vendor
- OpenACS
- Product
- OpenACS Bug Tracker
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 5, 2023CVE publishedPublication date reported by the CVE source.
- Nov 25, 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=n/a
What conditions does exploitation require?
What is affected?
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