Tuxedo vulnerabilitiesRanked by how likely they are to be used.

Product7 versions
The short answer

Tuxedo is made by Oracle. We track 16 published vulnerabilities listed under that exact name, across 7 versions. None of them is on the list of flaws known to be exploited today. Oracle lists newer releases under their own names, such as Tuxedo System and Applications Monitor, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Tuxedo listed under other names? Yes.

Oracle also lists Tuxedo under more specific names, such as Tuxedo System and Applications Monitor. 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.

Known exploited

Which Tuxedo vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Tuxedo 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. 81%

    JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration.

    CVSS7.5Published14 Dec 2021
  2. 67%

    By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout.

    CVSS9.8Published18 Jan 2022
  3. 64%

    JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker...

    CVSS8.8Published18 Jan 2022
  4. 54%

    CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw.

    CVSS8.8Published18 Jan 2022
  5. 12%

    The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack.

    CVSS5.9Published30 Oct 2018
  6. 11%

    ssl/s2_srvr.c in OpenSSL 1.0.1 before 1.0.1r and 1.0.2 before 1.0.2f does not prevent use of disabled ciphers, which makes it easier for man-in-the-middle attackers to defeat cryptographic protection mechanisms by...

    CVSS5.9Published15 Feb 2016
  7. 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
  8. 4.7%

    The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack.

    CVSS5.9Published29 Oct 2018
  9. 3.4%

    Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'.

    CVSS4.7Published15 Nov 2018
Precursor Intelligence

Running Tuxedo? 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 16 published vulnerabilities listed under the name Tuxedo, across 7 versions.

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

Oracle also lists Tuxedo under more specific names, such as Tuxedo System and Applications Monitor. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

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