Communications Cloud Native Core Policy vulnerabilitiesAnd the versions its exploited flaws hit.

Product3 known exploited11 versions
The short answer

Communications Cloud Native Core Policy is made by Oracle. We track 125 published vulnerabilities in it, across 11 versions. 3 of them are on the list of flaws known to be exploited, the newest added on 10 March 2023. If you run Communications Cloud Native Core Policy, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Communications Cloud Native Core Policy flaw added to the known-exploited list is CVE-2021-39144, on 10 March 2023. We keep watching the known-exploited list.

Versions

Which versions of Communications Cloud Native Core Policy do the exploited flaws hit?

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

  • CVE-2021-39144Exploited list, 10 Mar 2023

    XStream Remote Code Execution Vulnerability

    1.14.0
  • CVE-2022-22963Exploited list, 25 Aug 2022

    VMware Tanzu Spring Cloud Function Remote Code Execution Vulnerability

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

    Spring Framework JDK 9+ Remote Code Execution Vulnerability

    1.15.022.1.0
Known exploited

Which Communications Cloud Native Core Policy 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. 8.5
    CVE-2021-39144HighKnown exploited
    XStream Remote Code Execution Vulnerability

    XStream contains a remote code execution vulnerability that allows an attacker to manipulate the processed input stream and replace or inject objects that result in the execution of a local command on the server.

    Chance of use98%Known exploited since10 Mar 2023
  2. 9.8
    CVE-2022-22963CriticalKnown exploited
    VMware Tanzu Spring Cloud Function Remote Code Execution Vulnerability

    When using routing functionality in VMware Tanzu's Spring Cloud Function, it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in remote code execution and access to...

    Chance of use>99%Known exploited since25 Aug 2022
  3. 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
Exploit likelihood

Which Communications Cloud Native Core Policy 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%

    Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups.

    CVSS5.9Published18 Dec 2021
  2. >99%
    CVE-2022-22963CriticalKnown exploited

    In Spring Cloud Function versions 3.1.6, 3.2.2 and older unsupported versions, when using routing functionality it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in...

    CVSS9.8Published1 Apr 2022
  3. >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
  4. 98%
    CVE-2021-39144HighKnown exploited

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

    CVSS8.5Published23 Aug 2021
  5. 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
  6. 87%

    The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104.

    CVSS7.5Published14 Jul 2020
  7. 85%

    Spring Cloud Config, versions 2.1.x prior to 2.1.2, versions 2.0.x prior to 2.0.4, and versions 1.4.x prior to 1.4.6, and older unsupported versions allow applications to serve arbitrary configuration files through...

    CVSS6.5Published6 May 2019
  8. 83%

    The org.h2.util.JdbcUtils.getConnection method of the H2 database takes as parameters the class name of the driver and URL of the database.

    CVSS9.8Published10 Jan 2022
  9. 78%

    For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory.

    CVSS5.3Published9 Jun 2021
  10. 75%

    Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when...

    CVSS5.3Published12 Jul 2021
Precursor Intelligence

Running Communications Cloud Native Core Policy? 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 125 published vulnerabilities listed under the name Communications Cloud Native Core Policy, across 11 versions. The most recent Communications Cloud Native Core Policy flaw added to the known-exploited list is CVE-2021-39144, on 10 March 2023.

3 are on the list of flaws known to be exploited. The most recently added are CVE-2021-39144, CVE-2022-22963 and CVE-2022-22965.

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

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