CVE-2015-7364: CSRF
First published: Wed Oct 14 2015(Updated: )
The HTML_Quickform library, as used in Revive Adserver before 3.2.2, allows remote attackers to bypass the CSRF protection mechanism via an empty token.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Revive Adserver | <=3.2.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://packetstormsecurity.com/files/133893/Revive-Adserver-3.2.1-CSRF-XSS-Local-File-Inclusion.html
- http://seclists.org/fulldisclosure/2015/Oct/32
- http://www.revive-adserver.com/security/revive-sa-2015-001
- http://www.securityfocus.com/archive/1/536633/100/0/threaded
- https://github.com/revive-adserver/revive-adserver/commit/288f81cc
Frequently Asked Questions
What is the severity of CVE-2015-7364?
CVE-2015-7364 has a medium severity rating due to the potential for CSRF attacks that can compromise user sessions.
How do I fix CVE-2015-7364?
To fix CVE-2015-7364, upgrade Revive Adserver to version 3.2.2 or later.
What type of vulnerability is CVE-2015-7364?
CVE-2015-7364 is a Cross-Site Request Forgery (CSRF) vulnerability.
Who is affected by CVE-2015-7364?
CVE-2015-7364 affects users of Revive Adserver versions prior to 3.2.2.
What can attackers achieve with CVE-2015-7364?
Attackers can bypass the CSRF protection mechanism, potentially allowing unauthorized actions on behalf of users.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/remedy
- agent/weakness
- agent/severity
- agent/references
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/revive-adserver
- canonical/revive adserver
- version/revive adserver/3.2.1