Skip to content
VulniPulse
Advisory severityMedium5.9Red Hat Linux

Medium [CVE-2024-58375] Sensitive information disclosure via static evaluation

This medium-severity Red Hat Linux advisory covers CVE-2024-58375.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2024-58375 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

OpenTofu versions 1.8.0 through 1.8.2 do not properly restrict sensitive variables and locals when users have opted into static evaluation of module sources, versions, and backend configurations. As a result, values marked as sensitive may be exposed through these configuration elements instead of producing an error.

This is fixed in OpenTofu 1.8.3, which adds explicit errors to prevent the use of sensitive values in these contexts. A flaw was found in OpenTofu.

This oversight can lead to the exposure of values intended to be sensitive through these configuration elements, resulting in an information disclosure vulnerability. While the vulnerability could expose sensitive variables, the attack complexity is high, requiring specific user configurations to be in place for exploitation.

Red Hat severity: Moderate — CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N). Weakness: CWE-497.

Red Hat lists Red Hat Hardened Images as not affected.

Affected versions
  • 1.8.0
  • 1.8.2

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Fixed versions
  • 1.8.3

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Mitigation

Upgrade to a fixed release: 1.8.3. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.