First published: Tue Mar 28 2017(Updated: )
Revive Adserver before 3.2.5 and 4.0.0 suffers from Special Element Injection. Usernames weren't properly sanitised when creating users on a Revive Adserver instance. Especially, control characters were not filtered, allowing apparently identical usernames to co-exist in the system, due to the fact that such characters are normally ignored when an HTML page is displayed in a browser. The issue could have therefore been exploited for user spoofing, although elevated privileges are required to create users within Revive Adserver.
Credit: support@hackerone.com
Affected Software | Affected Version | How to fix |
---|---|---|
Revive Adserver | <=3.2.4 | |
Revive Adserver | =4.0.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-9471 is considered a high severity vulnerability due to its potential impact on user management and access control.
To fix CVE-2016-9471, upgrade to Revive Adserver version 3.2.5 or later, or version 4.0.1 or later to ensure proper username sanitization.
CVE-2016-9471 affects Revive Adserver versions prior to 3.2.5 and 4.0.0.
CVE-2016-9471 exploits a failure to properly sanitize usernames during user creation, allowing control characters to persist.
The consequences of CVE-2016-9471 include the potential for identity confusion among users due to duplicate usernames and unauthorized access.