Security readout for executives and security teams
Plain-English summary
OpenTofu 1.8.0 through 1.8.2 can expose values designated as sensitive when static evaluation is enabled for module sources, versions, or backend configurations. This could disclose infrastructure credentials or other secrets used in affected configurations. OpenTofu 1.8.3 prevents these uses by returning errors.
Executive priority
Prioritize remediation where OpenTofu manages privileged infrastructure credentials and static evaluation is enabled. Upgrade promptly, then assess whether sensitive values entered the affected contexts. Broader emergency action is not supported without evidence of exposure or exploitation.
Technical view
The flaw is an information exposure weakness, classified as CWE-497. Sensitive variables and locals were not properly rejected during opted-in static evaluation of module source, version, and backend configuration expressions. The supplied CVSS 4.0 score is 8.7, reflecting potentially high confidentiality impact without stated integrity or availability impact.
Likely exposure
Exposure requires OpenTofu 1.8.0, 1.8.1, or 1.8.2, opted-in static evaluation, and sensitive values referenced in the affected configuration contexts. Deployments outside those conditions are not shown as vulnerable by the supplied description. The evidence does not quantify deployment prevalence or identify specific leaked secrets.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not listed as KEV in the supplied data. The issue concerns unintended secret disclosure during configuration evaluation rather than a demonstrated compromise technique. No public exploitation evidence is provided here.
Researcher notes
The narrative identifies versions 1.8.0 through 1.8.2 as affected and 1.8.3 as fixed. The structured affected entry in the bundle is ambiguous, so version conclusions should follow the explicit narrative and vendor advisory. Available evidence establishes the flaw and fix but does not establish real-world exploitation or disclosure locations.
Mitigation direction
- Upgrade affected OpenTofu installations to version 1.8.3 or later.
- Review module source, version, and backend expressions for references to sensitive variables or locals.
- Restrict access to configuration outputs and related artifacts until exposure is assessed.
- Rotate affected secrets if review confirms they were exposed.
Validation and detection
- Inventory OpenTofu versions and identify installations running 1.8.0 through 1.8.2.
- Determine whether static evaluation was enabled in each affected installation.
- Inspect module source, version, and backend expressions for sensitive-value references.
- Confirm upgraded installations reject sensitive values in these contexts.
- Review accessible artifacts for evidence of disclosed values without unnecessarily reproducing secrets.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-497: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-58375 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-wpr2-j6gr-pjw9)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: OpenTofu before 1.8.3 Secret Variable Leaking via Static EvaluationCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive System Information to an Unauthorized Control Sphere
Exposure of Sensitive System Information to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.