Communications Design Studio vulnerabilitiesRanked by how likely they are to be used.

Product10 versions
The short answer

Communications Design Studio is made by Oracle. We track 15 published vulnerabilities in it, across 10 versions. None of them is on the list of flaws known to be exploited today. If you run Communications Design Studio, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Communications Design Studio vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Communications Design Studio's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Communications Design Studio 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. 28%

    In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects.

    CVSS7.3Published20 Aug 2019
  2. 21%

    Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.

    CVSS7.2Published15 Feb 2021
  3. 12%

    In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the...

    CVSS6.5Published19 Sep 2020
  4. 11%

    Apache Axis 1.x up to and including 1.4 is vulnerable to a cross-site scripting (XSS) attack in the default servlet/services.

    CVSS6.1Published2 Aug 2018
  5. 11%

    In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to...

    CVSS4.8Published13 Apr 2021
  6. 9.2%

    The ZlibDecoders in Netty 4.1.x before 4.1.46 allow for unbounded memory allocation while decoding a ZlibEncoded byte stream.

    CVSS7.5Published7 Apr 2020
  7. 7.3%

    Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.

    CVSS5.3Published15 Feb 2021
  8. 4.9%

    Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

    CVSS5.9Published30 Mar 2021
  9. 4.3%

    In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application because of missing validation of a sqlite_stat1 sz field, aka a "severe division by zero in the query planner."

    CVSS6.5Published9 Sep 2019
Precursor Intelligence

Running Communications Design Studio? 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 15 published vulnerabilities listed under the name Communications Design Studio, across 10 versions.

None of Communications Design Studio's vulnerabilities is on the list of flaws known to be exploited today.

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