CVE-2022-25374
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHashiCorp Terraform Enterprise v202112-1, v202112-2, v202201-1, and v202201-2 were configured to log inbound HTTP requests in a manner that may capture sensitive data. Fixed in v202202-1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceHashiCorp Terraform Enterprise versions v202112-1 through v202201-2 had insecure default logging configuration that captured sensitive data from inbound HTTP requests. This could expose credentials, tokens, or other sensitive information in application logs. The vulnerability was addressed in version v202202-1.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 202202-1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Terraform Enterprise versionDetermine the installed version of Terraform Enterprise using the system's version reporting mechanism or administrative interfaceAffected if The installed version is v202112-1, v202201-1, v202201-2, or any version prior to v202202-1
-
Locate logging configurationAccess the Terraform Enterprise logging configuration files or settingsAffected if The logging configuration captures inbound HTTP request bodies, headers, or parameters by default
-
Examine application logsReview Terraform Enterprise application logs for the presence of sensitive data such as API tokens, passwords, secret keys, or authentication credentials in request contentAffected if Logs contain exposed credentials, tokens, or other sensitive information from HTTP requests
-
Verify log storage accessCheck who has access to the Terraform Enterprise log files or log aggregation systemsAffected if Logs with potential sensitive data are accessible to unauthorized users or systems
A user is affected if their Terraform Enterprise version is below v202202-1 and the logs contain sensitive data from inbound HTTP requests due to the default logging configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped202202-1
Upgrade Terraform Enterprise to v202202-1 or later. Review existing logs for any sensitive data exposure and rotate potentially compromised credentials.
Terraform Enterprise v202202-1 or later
- Verify current Terraform Enterprise version by checking the admin console or using the API
- Review the upgrade documentation for Terraform Enterprise
- Plan and schedule the upgrade during a maintenance window
- Upgrade Terraform Enterprise to version 202202-1 or later
- After upgrade, verify that HTTP request logging no longer captures sensitive data by reviewing log configurations
- Monitor logs to confirm the fix is working properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25374 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data