Media Experience Engine vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited3 versions
The short answer

Media Experience Engine is made by Cisco. We track 1 published vulnerability listed under that exact name, across 3 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 3 November 2021. Cisco lists newer releases under their own names, such as Media Experience Engine 5600, so check those pages too.

Check your version

The most recent Media Experience Engine flaw added to the known-exploited list is CVE-2017-9805, on 3 November 2021. We keep watching the known-exploited list.

Other names

Is Media Experience Engine listed under other names? Yes.

Cisco also lists Media Experience Engine under more specific names, such as Media Experience Engine 5600. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Versions

Which versions of Media Experience Engine do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2017-9805Exploited list, 3 Nov 2021

    Apache Struts Deserialization of Untrusted Data Vulnerability

    3.53.5.2
Known exploited

Which Media Experience Engine vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 8.1
    CVE-2017-9805HighKnown exploited
    Apache Struts Deserialization of Untrusted Data Vulnerability

    Apache Struts REST Plugin uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to remote code execution when deserializing XML payloads.

    Chance of use>99%Known exploited since3 Nov 2021
Exploit likelihood

Which Media Experience Engine flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2017-9805HighKnown exploited

    The REST Plugin in Apache Struts 2.1.1 through 2.3.x before 2.3.34 and 2.5.x before 2.5.13 uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to Remote...

    CVSS8.1Published15 Sep 2017
Precursor Intelligence

Running Media Experience Engine? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 1 published vulnerability listed under the name Media Experience Engine, across 3 versions. The most recent Media Experience Engine flaw added to the known-exploited list is CVE-2017-9805, on 3 November 2021.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2017-9805.

Cisco also lists Media Experience Engine under more specific names, such as Media Experience Engine 5600. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Each flaw names its own versions, usually as ranges. The newest, CVE-2017-9805, affects 3.5, 3.5.2. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Media Experience Engine. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.