| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Revive Adserver up to 3.2.2. Impacted is an unknown function. Performing a manipulation results in cross-site request forgery. This vulnerability is identified as CVE-2016-9127. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Revive Adserver up to 3.2.2 (Advertising Software). It has been classified as problematic. This affects some unknown functionality. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:
Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF). The password recovery form in Revive Adserver is vulnerable to CSRF attacks. This vulnerability could be exploited to send a large number of password recovery emails to the registered users, especially in conjunction with a bug that caused recovery emails to be sent to all the users at once. Both issues have been fixed.
The bug was discovered 03/02/2016. The weakness was released 03/28/2017 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2016-9127 since 10/31/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 390 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 3.2.3 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-98964, VDB-98963, VDB-98960 and VDB-98958. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.3
VulDB Base Score: 4.3
VulDB Temp Score: 3.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Adserver 3.2.3
Patch: github.com
Timeline
03/02/2016 🔍10/31/2016 🔍
03/27/2017 🔍
03/28/2017 🔍
03/28/2017 🔍
11/22/2022 🔍
Sources
Advisory: 3aaebcc765797d2c684e031f2836e0a69d6b7bc2Status: Not defined
CVE: CVE-2016-9127 (🔍)
GCVE (CVE): GCVE-0-2016-9127
GCVE (VulDB): GCVE-100-98961
OSVDB: - CVE-2016-9127 - Revive Adserver - Cross-Site Request Forgery Issue
See also: 🔍
Entry
Created: 03/28/2017 22:12Updated: 11/22/2022 15:01
Changes: 03/28/2017 22:12 (59), 09/14/2020 20:21 (2), 11/22/2022 15:01 (5)
Complete: 🔍
Cache ID: 216:A2A:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.