<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 15:53:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-2700 — Quarkus-core: leak of local configuration properties into quarkus applications</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-2700</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; quarkus-core, Red Hat HawtIO 4.0.0 for Red Hat build of Apache Camel 4, Red Hat AMQ Streams 2.7.0, Red Hat build of Apicurio Registry 2.6.1 GA, Red Hat build of Quarkus 3.2.12.Final, Red Hat build of Quarkus 3.8.4.redhat, Red Hat RHOSS-1.33-RHEL-8, Red Hat build of Apache Camel 4 for Quarkus 3, Red Hat build of Apache Camel - HawtIO 4, Red Hat Build of Keycloak and 4 more&lt;/p&gt;
&lt;p&gt;A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application&amp;#39;s build, therefore, running the resulting application inherits the values captured at build time. Some local environment variables may have been set by the developer or CI environment for testing purposes, such as dropping the database during application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application, which can lead to dangerous behavior if the application does not override these values. This behavior only happens for configuration properties from the `quarkus.*` namespace. Application-specific properties are not captured.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; quarkus-core, Red Hat HawtIO 4.0.0 for Red Hat build of Apache Camel 4, Red Hat AMQ Streams 2.7.0, Red Hat build of Apicurio Registry 2.6.1 GA, Red Hat build of Quarkus 3.2.12.Final, Red Hat build of Quarkus 3.8.4.redhat, Red Hat RHOSS-1.33-RHEL-8, Red Hat build of Apache Camel 4 for Quarkus 3, Red Hat build of Apache Camel - HawtIO 4, Red Hat Build of Keycloak and 4 more&lt;/p&gt;
&lt;p&gt;A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application&amp;#39;s build, therefore, running the resulting application inherits the values captured at build time. Some local environment variables may have been set by the developer or CI environment for testing purposes, such as dropping the database during application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application, which can lead to dangerous behavior if the application does not override these values. This behavior only happens for configuration properties from the `quarkus.*` namespace. Application-specific properties are not captured.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-2700</guid>
    </item>
  </channel>
</rss>
