Quarkus-core: tls protocol configured with quarkus.http.ssl.protocols is not enforced, client can enforce weaker supported tls protocol
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | Red Hat build of Quarkus 2.13.8.Final | affected |
|
||||||
| Red Hat | Red Hat build of Quarkus 2.13.8.Final | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat build of Quarkus 2.13.8.Final | |||
| io.quarkus/quarkus-grpc:2.13.8.Final-redhat-00004 | cpe:/a:redhat:quarkus:2.13::el8 | RHSA-2023:3809 | 2023-06-29T00:00:00Z |
| io.quarkus/quarkus-vertx-http:2.13.8.Final-redhat-00004 | cpe:/a:redhat:quarkus:2.13::el8 | RHSA-2023:3809 | 2023-06-29T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-1937 | 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. |
Github GHSA |
GHSA-3fhx-3vvg-2j84 | quarkus-core vulnerable to client driven TLS cipher downgrading |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.882% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.