Skip to content
Fencer Vulns
high 7.4

CVE-2024-12397 json

Io.quarkus.http/quarkus-http-core: quarkus http cookie smuggling

published 2024-12-12 22 mo ago modified 2026-11-05 3 d ago also GHSA-cxrx-q234-m22m , EUVD-2024-3462

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

A flaw was found in Quarkus-HTTP, which incorrectly parses cookies with certain value-delimiting characters in incoming requests. This issue could allow an attacker to construct a cookie value to exfiltrate HttpOnly cookie values or spoof arbitrary additional cookie values, leading to unauthorized data access or modification. The main threat from this flaw impacts data confidentiality and integrity.

Patch / fix

  • maven io.quarkus.http:quarkus-http-core 5.3.4
  • Red Hat Cryostat 4 on RHEL 9 0.5.0-6, 4.0.0-7
  • Red Hat Red Hat build of Keycloak 26.2 26.2-3, 26.2.4-2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-12397 updated cvss 7.4

io.quarkus.http/quarkus-http-core: Quarkus HTTP Cookie Smuggling

  • Red Hat Cryostat 3 quarkus-http-core Red Hat build of Apache Camel 4 for Quarkus 3 quarkus-cxf-bom, quarkus-camel-bom Red Hat build of Apicurio Registry 2 quarkus-http-core Red Hat Build of Keycloak quarkus-http-core
    affected: workaround, no fix available “Currently, no mitigation is available for this vulnerability.”
  • Red Hat build of OptaPlanner 8 quarkus-http-core Red Hat Fuse 7 quarkus-http-core
    affected: workaround, no fix planned “Currently, no mitigation is available for this vulnerability.”
  • Red Hat Integration Camel K 1 quarkus-http-core Red Hat Process Automation 7 quarkus-http-core Red Hat streams for Apache Kafka quarkus-http-core
    affected: workaround, no fix available “Currently, no mitigation is available for this vulnerability.”
  • Red Hat Cryostat 4 on RHEL 9 cryostat/cryostat-rhel9 4.0.0-7, cryostat/cryostat-db-rhel9 4.0.0-7, cryostat/jfr-datasource-rhel9 4.0.0-7, cryostat/cryostat-reports-rhel9 4.0.0-7, cryostat/cryostat-storage-rhel9 4.0.0-7, cryostat/cryostat-rhel9-operator 4.0.0-7, +5 more
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:3018
  • Red Hat HawtIO HawtIO 4.2.0
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:8761
  • Red Hat Build of Keycloak
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHBA-2025:7525
  • Red Hat build of Keycloak 26.2 rhbk/keycloak-rhel9 26.2-3, rhbk/keycloak-rhel9-operator 26.2-3, rhbk/keycloak-operator-bundle 26.2.4-2
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHBA-2025:7639
  • Red Hat build of Quarkus 3.15.3
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:0900
show 1 more
  • Red Hat JBoss Enterprise Application Platform 8 quarkus-http-core Red Hat JBoss Enterprise Application Platform Expansion Pack quarkus-http-core
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
22 mo ago

Exploit prediction

0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven io.quarkus.http:quarkus-http-core
<5.3.4
5.3.4

Affected products

  • Red Hat Cryostat 4 on RHEL 9
  • Red Hat HawtIO HawtIO 4.2.0
  • Red Hat Red Hat Build of Keycloak
  • Red Hat Red Hat build of Keycloak 26.2
  • Red Hat Red Hat build of Quarkus 3.15.3
  • Red Hat Cryostat 3
  • Red Hat Red Hat build of Apache Camel 4 for Quarkus 3
  • Red Hat Red Hat build of Apicurio Registry 2
  • Red Hat Red Hat build of OptaPlanner 8
  • Red Hat Red Hat Fuse 7
  • Red Hat Red Hat Integration Camel K 1
  • Red Hat Red Hat JBoss Enterprise Application Platform 8
  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
  • Red Hat Red Hat Process Automation 7
  • Red Hat streams for Apache Kafka

Classification

Weakness
  • CWE-444 Inconsistent Interpretation of HTTP Requests

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.