CVE-2016-9455: CSRF

Published Mar 28, 2017
·
Updated

Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF). A number of scripts in Revive Adserver's user interface are vulnerable to CSRF attacks: www/admin/banner-acl.php, www/admin/banner-activate.php, www/admin/banner-advanced.php, www/admin/banner-modify.php, www/admin/banner-swf.php, www/admin/banner-zone.php, www/admin/tracker-modify.php.

Affected Software

1 affected component
revive-adserver Revive Adserver<=3.2.2

Event History

Mar 28, 2017
CVE Published
via MITRE·02:46 AM
Data Sourced
via MITRE·02:46 AM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2016-9455?

CVE-2016-9455 is classified as a medium severity vulnerability due to its potential for exploitation via CSRF attacks.

2

How do I fix CVE-2016-9455?

To fix CVE-2016-9455, upgrade to Revive Adserver version 3.2.3 or later.

3

What types of attacks can be carried out exploiting CVE-2016-9455?

Exploiting CVE-2016-9455 can allow attackers to perform unauthorized actions on behalf of authenticated users.

4

Which versions of Revive Adserver are affected by CVE-2016-9455?

CVE-2016-9455 affects all versions of Revive Adserver prior to 3.2.3.

5

Is user authentication at risk due to CVE-2016-9455?

Yes, user authentication can be compromised as CVE-2016-9455 allows CSRF attacks that exploit authenticated users' sessions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203