Integration Camel K vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited1 versions
The short answer

Integration Camel K is made by Red Hat. We track 20 published vulnerabilities in it, across 1 version. 1 of them is on the list of flaws known to be exploited, the newest added on 10 October 2023. If you run Integration Camel K, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Integration Camel K flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023. We keep watching the known-exploited list.

Versions

Which versions of Integration Camel K do the exploited flaws hit?

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

Known exploited

Which Integration Camel K vulnerabilities are being exploited?

1 flaw is 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. 7.5
    CVE-2023-44487HighKnown exploited
    HTTP/2 Rapid Reset Attack Vulnerability

    HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).

    Chance of use>99%Known exploited since10 Oct 2023
Exploit likelihood

Which Integration Camel K 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-2023-44487HighKnown exploited

    The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

    CVSS7.5Published10 Oct 2023
  2. 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
  3. 2.6%

    A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests.

    CVSS7.5Published21 Aug 2024
  4. 1.8%

    A flaw was found in undertow. This issue makes achieving a denial of service possible due to an unexpected handshake status updated in SslConduit, where the loop never terminates.

    CVSS7.5Published14 Sep 2023
  5. 1.7%

    A flaw was found in Undertow. A buffer leak on the incoming WebSocket PONG message may lead to memory exhaustion.

    CVSS7.5Published23 Aug 2022
  6. 1.5%

    A flaw was found in XNIO, specifically in the notifyReadClosed method.

    CVSS7.5Published26 Aug 2022
  7. 1.4%

    A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions.

    CVSS8.1Published20 Sep 2023
  8. 1.3%

    A flaw was found in codeplex-codehaus. A directory traversal attack (also known as path traversal) aims to access files and directories stored outside the intended folder.

    CVSS7.5Published25 Sep 2023
  9. 1.3%

    A flaw was found in the fabric8 kubernetes-client in version 4.2.0 and after.

    CVSS7.4Published16 Mar 2021
  10. 1.3%

    A flaw was found in Undertow. A potential security issue in flow control handling by the browser over HTTP/2 may cause overhead or a denial of service in the server.

    CVSS7.5Published31 Aug 2022
Precursor Intelligence

Running Integration Camel K? 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 20 published vulnerabilities listed under the name Integration Camel K, across 1 version. The most recent Integration Camel K flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2023-44487.

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