CyberSecBulletin
CVE-2024-2700NVD status: Deferred

HawtIO 4.0.0 for Red Hat build of Apache Camel 4: Cleartext Storage of Sensitive Information in an Environment Variable

Published Updated By the CyberSecBulletin desk

CVE-2024-2700 is a high-severity cleartext storage of sensitive information in an environment variable vulnerability in HawtIO 4.0.0 for Red Hat build of Apache Camel 4 from Red Hat, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.31% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of HawtIO 4.0.0 for Red Hat build of Apache Camel 4 you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatHawtIO 4.0.0 for Red Hat build of Apache Camel 4Not specified in the recordNot stated
Red HatRed Hat AMQ Streams 2.7.0Not specified in the recordNot stated
Red HatRed Hat build of Apicurio Registry 2.6.1 GANot specified in the recordNot stated
Red HatRed Hat build of Quarkus 3.2.12.FinalNot specified in the recordNot stated
Red HatRed Hat build of Quarkus 3.8.4.redhatNot specified in the recordNot stated
Red HatRHOSS-1.33-RHEL-8Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel 4 for Quarkus 3Not specified in the recordNot stated
Red HatRed Hat Build of KeycloakNot specified in the recordNot stated
Red HatRed Hat build of OptaPlanner 8Not specified in the recordNot stated
Red HatRed Hat build of QuarkusNot specified in the recordNot stated
Red HatRed Hat Integration Camel K 1Not specified in the recordNot stated
Red HatRed Hat Integration Camel Quarkus 2Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (redhat.com).

Official description

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

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Cleartext Storage of Sensitive Information in an Environment Variable

The product uses an environment variable to store unencrypted sensitive information.

How developers prevent this class of flaw

  • If the environment variable is not necessary for the desired behavior, then remove it entirely, or clear it to an empty value.

More Cleartext Storage of Sensitive Information in an Environment Variable vulnerabilities (CWE-526)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in HawtIO 4.0.0 for Red Hat build of Apache Camel 4

All HawtIO 4.0.0 for Red Hat build of Apache Camel 4 vulnerabilities

Recent Cleartext Storage of Sensitive Information in an Environment Variable vulnerabilities

Spotted an error? Tell us.