Revive Adserver up to 3.2.4/4.0.0 Username Control Character unknown vulnerability

entryeditHistoryDiffjsonxmlCTI
CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.1$0-$5k0.00

A vulnerability classified as critical was found in Revive Adserver up to 3.2.4/4.0.0 (Advertising Software). Affected by this vulnerability is an unknown part of the component Username Handler. The manipulation as part of a Control Character leads to a unknown weakness. The CWE definition for the vulnerability is CWE-75. As an impact it is known to affect confidentiality, and integrity. The summary by CVE 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.

The bug was discovered 09/28/2016. The weakness was presented 03/28/2017 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2016-9471 since 11/19/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 180 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 3.2.5 eliminates this vulnerability.

See 98984 and 98982 for similar entries.

Productinfoedit

Type

Vendor

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 3.1
NVD Vector: 🔍

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfoedit

Class: Unknown
CWE: CWE-75
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍

Countermeasuresinfoedit

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Adserver 3.2.5

Timelineinfoedit

09/28/2016 🔍
11/19/2016 +52 days 🔍
03/27/2017 +128 days 🔍
03/28/2017 +1 days 🔍
03/28/2017 +0 days 🔍
08/23/2020 +1244 days 🔍

Sourcesinfoedit

Advisory: github.com
Status: Not defined

CVE: CVE-2016-9471 (🔍)
OSVDB: - CVE-2016-9471 - Revive Adserver - Spoofing Issue

See also: 🔍

Entryinfoedit

Created: 03/28/2017 10:17 PM
Updated: 08/23/2020 12:05 PM
Changes: (2) vulnerability_discoverydate source_osvdb_title
Complete: 🔍

Comments

No comments yet. Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!