Revive Adserver up to 4.2.0 XML-RPC Invocation Script unserialize Parameter deserialization
|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.
A vulnerability was found in Revive Adserver up to 4.2.0 (Advertising Software) and classified as critical. Affected by this issue is the function
unserialize of the component XML-RPC Invocation Script Handler. The manipulation as part of a Parameter leads to a privilege escalation vulnerability. Using CWE to declare the problem leads to CWE-502. Impacted is confidentiality, integrity, and availability. CVE summarizes:
An attacker could send a specifically crafted payload to the XML-RPC invocation script and trigger the unserialize() call on the "what" parameter in the "openads.spc" RPC method. Such vulnerability could be used to perform various types of attacks, e.g. exploit serialize-related PHP vulnerabilities or PHP object injection. It is possible, although unconfirmed, that the vulnerability has been used by some attackers in order to gain access to some Revive Adserver instances and deliver malware through them to third party websites. This vulnerability was addressed in version 4.2.0.
The bug was discovered 04/23/2019. The weakness was disclosed 05/06/2019. This vulnerability is handled as CVE-2019-5434 since 01/04/2019. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a private exploit are known. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 06/07/2020).
It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 13 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry 134401 is pretty similar.
CVSSv3VulDB Meta Base Score: 8.5
VulDB Meta Temp Score: 8.1
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
ExploitingClass: Privilege escalation
Price Prediction: 🔍
Current Price Estimation: 🔍
Threat IntelligenceThreat: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔍
04/23/2019 +109 days 🔍
05/06/2019 +13 days 🔍
05/06/2019 +0 days 🔍
06/07/2020 +398 days 🔍
SourcesStatus: Not defined
CVE: CVE-2019-5434 (🔍)
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
EntryCreated: 05/06/2019 09:17 PM
Updated: 06/07/2020 09:33 AM
Changes: (1) vulnerability_discoverydate
Do you need the next level of professionalism?
Upgrade your account now!