CVE Tools
Track your stack

CVE-2017-5641

Previous versions of Apache Flex BlazeDS (4.7.2 and earlier) did not restrict which types were allowed for AMF(X) object deserialization by default. During the deserialization process code is execu...

Public exploit available. Not confirmed exploited in the wild yet. Fixed versions are out.

CVSS 3.19.8CriticalEPSS percentile98th21% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
Public exploit: 1 sourceFix5 products2 fixed builds listed below

Published Updated Sources: CVE.org, NVD, GitHub, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Apache Software Foundation Apache Flex Blaze DSAffected: before 4.7.3Upgrade to: not statedStated by: CVE record
  • Maven org.apache.flex.blazeds:flex-messaging-coreAffected: < 4.7.3Upgrade to: 4.7.3Stated by: GitHub advisory
  • Maven org.apache.flex.blazeds:flex-messaging-remotingAffected: < 4.7.3Upgrade to: 4.7.3Stated by: GitHub advisory
  • Apache Flex BlazedsAffected: ≤ 4.7.2Upgrade to: after 4.7.2Stated by: NVD
  • Hp Xp Command View Advanced EditionAffected: < 8.5.3-00Upgrade to: 8.5.3-00Stated by: NVD

Versions as the sources state them. 2 more products have version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Apache Flex BlazeDS unsafe deserialization

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS98th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

21% chance of exploitation activity in the next 30 days, which ranks it in the 98th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

A public exploit existed 67 days before the patch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Public exploit / PoCsource: github-poc
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 19 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Maven, not every advisory. This one: public exploit.