Critical

PHP Object Injection in Revive Adserver XML-RPC openads.spc (openads.spc RPC method)

IdentifiersCVE-2019-5434CWE-502· Deserialization of Untrusted Data

CVE-2019-5434 is a PHP object injection / unsafe deserialization issue in Revive Adserver’s XML-RPC invocation endpoint. An attacker can send a specially crafted XML-RPC request that invokes the "openads.spc" RPC method and supplies a malicious value in the "what" parameter, which is passed to PHP unserialize(). This allows attacker-controlled serialized data to be deserialized, enabling exploitation of PHP object injection gadget chains and other serialize/unserialize-related vulnerabilities. The issue was fixed in Revive Adserver 4.2.0.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can enable PHP object injection, which depending on available gadget chains in the application and its dependencies may lead to arbitrary code execution, unauthorized access to the adserver instance, and use of the compromised adserver to deliver malicious content (e.g., malware) to third-party websites via served advertisements. The content notes exploitation in the wild is possible but unconfirmed.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure of the XML-RPC invocation endpoint (e.g., restrict network access to trusted sources, disable or block XML-RPC invocation if not required) and monitor for suspicious XML-RPC requests targeting the openads.spc method and anomalous serialized payloads in the "what" parameter.

Remediation

Patch, then assume compromise.

Upgrade Revive Adserver to version 4.2.0 or later, where the vulnerability is addressed.

PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

ReviveRevive Adserverapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

2 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2