CVE-2016-9471
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with an admin-level account, but needs a user to act. Limited direct impact.
- Exploit odds
- 1.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.4% in the next 30 days (EPSS).
- Severity: 3.1 LOW (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.4% · EPSS, next 30 days
- Weakness
- CWE-75
- Record status
- Modified
Affected
- revive-adserver Revive Adserver ≤ 3.2.4
- revive-adserver Revive Adserver 4.0.0
Attack profile CVSS 3.0 · 3.1
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Raw vector
CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-9471.md and follow it. Check whether this project is affected by CVE-2016-9471. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/revive-adserver/revive-adserver/commit/05b1eceb
- https://www.revive-adserver.com/security/revive-sa-2016-002/
- https://github.com/revive-adserver/revive-adserver/commit/05b1eceb
- https://www.revive-adserver.com/security/revive-sa-2016-002/
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/