EUVD-2023-1937

Malicious code in bioql PyPI...

quarkus-core: Leak of local configuration properties into Quarkus applications

A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application's build, therefore, running the resulting application inherits the values captured at build time. Some local environment variables may have been...

Important: Red Hat Security Advisory: Apicurio Registry (container images) release and security update [ 2.6.1 GA ]

An update to the images for Red Hat build of Apicurio Registry is now available from the Red Hat Container Catalog. The purpose of this text-only errata is to inform you about the security issues fixed in this release. Red Hat Product Security has rated this update as having a security impact of...

RHEL 6 : io.quarkus_quarkus-core (Unpatched Vulnerability)

The remote Redhat Enterprise Linux 6 host has one or more packages installed that are affected by a vulnerability that has been acknowledged by the vendor but will not be patched. - quarkus-core: Leak of local configuration properties into Quarkus applications CVE-2024-2700 Note that Nessus has n...

RHEL 6 : quarkus-core (Unpatched Vulnerability)

The remote Redhat Enterprise Linux 6 host has one or more packages installed that are affected by a vulnerability that has been acknowledged by the vendor but will not be patched. - quarkus-core: Leak of local configuration properties into Quarkus applications CVE-2024-2700 Note that Nessus has n...

ai.timefold.solver:timefold-solver-quarkus (>=1.2.0 <=1.9.0), ai.timefold.solver:timefold-solver-quarkus-benchmark (>=1.2.0 <=1.9.0) +2610 more potentially affected by CVE-2024-2700 via io.quarkus:quarkus-core (>=3.3.0.CR1 <=3.8.3)

io.quarkus:quarkus-core MAVEN version =3.3.0.CR1, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =1.2.0, =0.0.10, =0.0.14 and more Source cves: CVE-2024-2700 Source a...

com.github.t1:wunderbar.demo.product (=3.3), com.mobiera.libs:aircast-api-jakarta (=1.3) +600 more potentially affected by CVE-2024-2700 via io.quarkus:quarkus-core (>=3.9.0.CR1 <=3.9.1)

io.quarkus:quarkus-core MAVEN version =3.9.0.CR1, =0.3.0, =0.2.3, =0.3.4, =0.9.3, =0.9.9, =3.3.0, =3.3.0.CR2 and more Source cves: CVE-2024-2700 Source advisory: OSV:GHSA-F8H5-V2VG-46RR...

ai.aletyx.kogito:aletyx-kogito-ai-addons-quarkus-adhoc-subprocess (>=0.1.0 <=0.2.0), ai.aletyx.kogito:aletyx-kogito-ai-addons-quarkus-adhoc-subprocess-storage-jpa (>=0.1.0 <=0.2.0) +6694 more potentially affected by CVE-2024-2700 via io.quarkus:quarkus-core (>=0.11.0 <=3.2.11.Final)

io.quarkus:quarkus-core MAVEN version =0.11.0, =0.1.0, =0.1.0, =0.0.2, =0.1.1, =0.2.0, =0.2.0, =0.2.0, =0.2.0, =0.2.11 and more Source cves: CVE-2024-2700 Source advisory: OSV:GHSA-F8H5-V2VG-46RR...

CVE-2024-2700 Quarkus-core: leak of local configuration properties into quarkus applications

A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application's build, therefore, running the resulting application inherits the values captured at build time. Some local environment variables may have been...

CVE-2024-2700

A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application's build, therefore, running the resulting application inherits the values captured at build time. Some local environment variables may have been...

PT-2024-21609 · Quarkus · Quarkus

Name of the Vulnerable Software and Affected Versions: Quarkus affected versions not specified Description: A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application's build, and the resulting applicatio...

ai.timefold.solver:timefold-solver-quarkus (>=0.8.38 <=0.8.42), ai.timefold.solver:timefold-solver-quarkus-benchmark (>=0.8.38 <=0.8.42) +3888 more potentially affected by CVE-2023-2974 via io.quarkus:quarkus-core (>=0.11.0 <=2.16.7.Final)

io.quarkus:quarkus-core MAVEN version =0.11.0, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.38, =0.8.42 and more Source cve...

CVE-2023-2974

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...

CVE-2023-2974

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...

CVE-2023-2974

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...

Design/Logic Flaw

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...

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

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...

CVE-2023-2974

CVE-2023-2974 affects quarkus-core. The vulnerability arises because the TLS protocol configured via quarkus.http.ssl.protocols is not enforced, allowing a client to force the use of a weaker supported TLS protocol. Documented impact includes potential compromise of confidentiality and integrity,...

CVE-2023-2974

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...