CVE-2016-9471
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| revive-adserver | revive_adserver | {"endIncluding":"3.2.4"} | |
| revive-adserver | revive_adserver | 4.0.0 | |
References
- https://github.com/revive-adserver/revive-adserver/commit/05b1eceb
- https://hackerone.com/reports/128181
- https://www.revive-adserver.com/security/revive-sa-2016-002/
- https://github.com/revive-adserver/revive-adserver/commit/05b1eceb
- https://hackerone.com/reports/128181
- https://www.revive-adserver.com/security/revive-sa-2016-002/
CWEs
CWE-75
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.