Vulnerability in Revive-Adserver Revive Adserver
CVE-2016-9471
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 3.1 (Low). Vector: CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N.
EPSS exploit prediction
EPSS: 0.014 (70.8th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 71st percentile — 70.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.014 · newest: 0.014 · change: 0.000
Affected products
- Revive-Adserver Revive Adserver — versions 4.0.0
- Revive Adserver All Versions Before 3.2.5 And 4.0.0 — versions Revive Adserver All versions before 3.2.5 and 4.0.0
Weakness classification (CWE)
References
- hackerone.com/reports/128181 (Permissions Required)
- github.com/revive-adserver/revive-adserver/commit/05b1eceb (Patch, Third Party Advisory)
- www.revive-adserver.com/security/revive-sa-2016-002/ (Patch, Vendor Advisory)
Frequently asked questions
- What is CVE-2016-9471?
- CVE-2016-9471 is a low-severity vulnerability in Revive-Adserver Revive Adserver, classified under CWE-75. CVSS score: 3.1/10. Published 2017-03-28.
- How severe is CVE-2016-9471?
- Low severity. CVSS v3 base score is 3.1 out of 10.