Skip to content
Fencer Vulns
medium 6.5

CVE-2023-2974 json

Quarkus-core: tls protocol configured with quarkus.http.ssl.protocols is not enforced, client can enforce weaker supported tls protocol

published 2023-07-04 3 y ago modified 2026-06-17 4 mo ago also GHSA-3fhx-3vvg-2j84 , EUVD-2023-1937

cvss
6.5
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 59%
public exploits
0
none known

Summary

A vulnerability was found in quarkus-core. This vulnerability occurs because the TLS protocol configured with quarkus.http.ssl.protocols is not enforced, and the client can force the selection of the weaker supported TLS protocol.

Patch / fix

  • maven io.quarkus:quarkus-core 2.16.8.Final
  • Red Hat Red Hat build of Quarkus 2.13.8.Final 2.13.8.Final-redhat-00004

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-2023-2974 updated cvss 6.5

quarkus-core: TLS protocol configured with quarkus.http.ssl.protocols is not enforced, client can enforce weaker supported TLS protocol

  • Red Hat build of Quarkus quarkus-vertx-http
    affected: no fix available
  • Red Hat build of Quarkus 2.13.8.Final quarkus-grpc 2.13.8.Final-redhat-00004, quarkus-vertx-http 2.13.8.Final-redhat-00004
    fixed: vendor fix RHSA-2023:3809
  • Red Hat build of Quarkus 2.13.8.Final jna 5.8.0, bson 4.7.2, db2 1.17.3, h2 2.1.214, jansi 1.18, jdom 1.1.3, +871 more
    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

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven io.quarkus:quarkus-core
<2.16.8.Final
2.16.8.Final

Affected products

  • Red Hat Red Hat build of Quarkus 2.13.8.Final

Classification

Weakness
  • CWE-757 Selection of Less-Secure Algorithm During Negotiation

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.