CVE-2024-2307

Public on

Last Modified: UTC

ModerateModerate ImpactWhat does this mean?
DescriptionStatementMitigationAdditional informationAffected PackagesCVSS Score DetailsWeakness (CWE)FAQ

Description

A flaw was found in osbuild-composer. A condition can be triggered that disables GPG verification for package repositories, which can expose the build phase to a Man-in-the-Middle attack, allowing untrusted code to be installed into an image being built.

A flaw was found in osbuild-composer. A condition can be triggered that disables GPG verification for package repositories, which can expose the build phase to a Man-in-the-Middle attack, allowing untrusted code to be installed into an image being built.

Statement

The race condition in osbuild-composer that leads to unintentional GPG verification disabling for third-party repositories introduces a moderate severity risk. While the issue can potentially allow the installation of untrusted code into built images, its impact is limited to scenarios where both a third-party repository with GPG-checked RPMs and another repository with GPG checking disabled are concurrently added. Additionally, the insecure setting winning due to the race condition further narrows the circumstances under which the vulnerability can be exploited. However, the potential for bypassing GPG verification in specific configurations poses a tangible risk to the integrity of built images, justifying its classification as a moderate severity issue.

The race condition in osbuild-composer that leads to unintentional GPG verification disabling for third-party repositories introduces a moderate severity risk. While the issue can potentially allow the installation of untrusted code into built images, its impact is limited to scenarios where both a third-party repository with GPG-checked RPMs and another repository with GPG checking disabled are concurrently added. Additionally, the insecure setting winning due to the race condition further narrows the circumstances under which the vulnerability can be exploited. However, the potential for bypassing GPG verification in specific configurations poses a tangible risk to the integrity of built images, justifying its classification as a moderate severity issue.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Additional information

  • Bugzilla 2268513: osbuild-composer: race condition may disable GPG verification for package repositories
  • CWE-362->CWE-347: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') leads to Improper Verification of Cryptographic Signature
  • FAQ: Frequently asked questions about CVE-2024-2307

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown
Red HatNVD

CVSS v3 Base Score

6.1

N/A

Attack Vector

Local

N/A

Attack Complexity

Low

N/A

Privileges Required

High

N/A

User Interaction

Required

N/A

Scope

Unchanged

N/A

Confidentiality Impact

High

N/A

Integrity Impact

High

N/A

Availability Impact

Low

N/A

CVSS v3 Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

For open source software shipped by multiple vendors, the CVSS base scores may vary for each vendor's version depending on the version they ship, how they ship it, the platform, and even how the software is compiled. This makes scoring of vulnerabilities difficult for third-party vulnerability databases such as NVD that only provide a single CVSS base score for each vulnerability. Red Hat scores reflect how a vulnerability affects our products specifically.

For more information, see https://access.redhat.com/solutions/762393.

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

  • "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
  • "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.

What can I do if my product is listed as "Will not fix"?

A "will not fix" status means that a fix for an affected product version is not planned or not possible due to complexity, which may create additional risk.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
  • Apply a mitigation (if one exists).
  • Open a support case to request a prioritization of releasing a fix for this vulnerability.

What can I do if my product is listed as "Fix deferred"?

A deferred status means that a fix for an affected product version is not guaranteed due to higher-priority development work.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Apply a mitigation (if one exists).
  • Open a support case to request a prioritization of releasing a fix for this vulnerability.
  • Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.

What is a mitigation?

A mitigation is an action that can be taken to reduce the impact of a security vulnerability, without deploying any fixes.

I have a Red Hat product but it is not in the above list, is it affected?

The listed products were found to include one or more of the components that this vulnerability affects. These products underwent a thorough evaluation to determine their affectedness by this vulnerability. Note that layered products (such as container-based offerings) that consume affected components from any of the products listed in this table may be affected and are not represented.

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

In order to maintain code stability and compatibility, Red Hat usually does not rebase packages to entirely new versions. Instead, we backport fixes and new features to an older version of the package we distribute. This can result in some security scanners that only consider the package version to report the package as vulnerable. To avoid this, we suggest that you use an approved vulnerability scanner from our Red Hat Vulnerability Scanner Certification program.

Want to get errata notifications? Sign up here.