Communications Policy Management vulnerabilitiesAnd the versions its exploited flaws hit.

Product3 known exploited63 versions
The short answer

Communications Policy Management is made by Oracle. We track 50 published vulnerabilities in it, across 63 versions. 3 of them are on the list of flaws known to be exploited, the newest added on 4 April 2022. If you run Communications Policy Management, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Communications Policy Management flaw added to the known-exploited list is CVE-2022-22965, on 4 April 2022. We keep watching the known-exploited list.

Versions

Which versions of Communications Policy Management do the exploited flaws hit?

Each exploited flaw lists the versions it affects, usually as ranges. "before 12.5.0" means every version up to, but not including, 12.5.0. Find your version, then patch.

  • CVE-2022-22965Exploited list, 4 Apr 2022

    Spring Framework JDK 9+ Remote Code Execution Vulnerability

    12.6.0.0.0
  • CVE-2018-11776Exploited list, 3 Nov 2021

    Apache Struts Remote Code Execution Vulnerability

    before 12.5.0
  • CVE-2020-17530Exploited list, 3 Nov 2021

    Apache Struts Remote Code Execution Vulnerability

    12.5.0
Known exploited

Which Communications Policy Management vulnerabilities are being exploited?

3 flaws are 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. 9.8
    CVE-2022-22965CriticalKnown exploited
    Spring Framework JDK 9+ Remote Code Execution Vulnerability

    Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding.

    Chance of use>99%Known exploited since4 Apr 2022
  2. 8.1
    CVE-2018-11776HighKnown exploited
    Apache Struts Remote Code Execution Vulnerability

    Apache Struts contains a vulnerability that allows for remote code execution under two circumstances.

    Chance of use>99%Known exploited since3 Nov 2021
  3. 9.8
    CVE-2020-17530CriticalKnown exploited
    Apache Struts Remote Code Execution Vulnerability

    Forced Object-Graph Navigation Language (OGNL) evaluation in Apache Struts, when evaluated on raw user input in tag attributes, can lead to remote code execution.

    Chance of use96%Known exploited since3 Nov 2021
Exploit likelihood

Which Communications Policy Management 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-2018-11776HighKnown exploited

    Apache Struts versions 2.3 to 2.3.34 and 2.5 to 2.5.16 suffer from possible Remote Code Execution when alwaysSelectFullNamespace is true (either by user or a plugin like Convention Plugin) and then: results are used...

    CVSS8.1Published22 Aug 2018
  2. >99%
    CVE-2022-22965CriticalKnown exploited

    A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding.

    CVSS9.8Published1 Apr 2022
  3. 97%

    Apache Struts 2.0.0 to 2.5.20 forced double OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.

    CVSS9.8Published14 Sep 2020
  4. 96%
    CVE-2020-17530CriticalKnown exploited

    Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.

    CVSS9.8Published11 Dec 2020
  5. 95%

    Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-dependent attackers to execute arbitrary code via vectors related to the (1)...

    CVSS10.0Published28 Jan 2015
  6. 89%

    In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a...

    CVSS7.5Published17 Jan 2020
  7. 85%

    XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream.

    CVSS8.0Published16 Nov 2020
  8. 82%

    XStream is a Java library to serialize objects to XML and back again.

    CVSS5.4Published23 Mar 2021
  9. 76%

    XStream is a Java library to serialize objects to XML and back again.

    CVSS6.1Published23 Mar 2021
  10. 76%

    XStream is a Java library to serialize objects to XML and back again.

    CVSS5.3Published23 Mar 2021
Precursor Intelligence

Running Communications Policy Management? 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 50 published vulnerabilities listed under the name Communications Policy Management, across 63 versions. The most recent Communications Policy Management flaw added to the known-exploited list is CVE-2022-22965, on 4 April 2022.

3 are on the list of flaws known to be exploited. The most recently added are CVE-2022-22965, CVE-2018-11776 and CVE-2020-17530.

Each flaw names its own versions, usually as ranges. The newest, CVE-2022-22965, affects 12.6.0.0.0. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Communications Policy Management. 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.