CVE-2024-47083
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 · uneditedPower Platform Terraform Provider allows managing environments and other resources within Power Platform. Versions prior to 3.0.0 have an issue in the Power Platform Terraform Provider where sensitive information, specifically the `client_secret` used in the service principal authentication, may be exposed in logs. This exposure occurs due to an error in the logging code that causes the `client_secret` to not be properly masked when logs are persisted or viewed. Users should upgrade to version 3.0.0 to receive a patched version of the provider that removes all logging of sensitive content. Users who have used this provider with the affected versions should take the following additional steps to mitigate the risk: Immediately rotate the `client_secret` for any service principal that has been configured using this Terraform provider. This will invalidate any potentially exposed secrets. Those who have set the `TF_LOG_PATH` environment variable or configured Terraform to persist logs to a file or an external system, consider disabling this until they have updated to a fixed version of the provider. Those who have existing logs that may contain the `client_secret` should remove or sanitize these logs to prevent unauthorized access. This includes logs on disk, in monitoring systems, or in logging services.
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 · high confidenceThe Power Platform Terraform Provider versions before 3.0.0 fail to properly mask the client_secret in log output. When logging is enabled (via TF_LOG_PATH or similar), the plaintext client_secret used for service principal authentication is written to logs, allowing unauthorized access to these credentials.
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<= 3.0.0CVSS 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 the Power Platform Terraform Provider version in useInspect the version constraint in your Terraform configuration files (e.g., required_providers block in main.tf or versions.tf) or check the .terraform.lock.hcl file for the provider versionAffected if The provider version is 3.0.0 or lower
-
Determine if Terraform logging is enabledCheck for environment variables TF_LOG, TF_LOG_PATH, TF_LOG_CORE, or TF_LOG_PROVIDER being set to a non-empty value, or check if a log file path is configuredAffected if Any of these logging environment variables are set or a log path is configured
-
Inspect log files for plaintext client_secret valuesIf logging is enabled, search the log files (at TF_LOG_PATH location or default terraform.log) for the literal string 'client_secret' or patterns matching secret values that appear unmasked in plaintextAffected if Logs contain unmasked client_secret values in plaintext form
-
Review all log locations for potential credential exposureCheck all terraform log directories and any persisted log files that may have been created while using provider versions <= 3.0.0Affected if Any log files exist from prior runs with the vulnerable provider version
You are affected if you use Power Platform Terraform Provider version 3.0.0 or lower AND have Terraform logging enabled, as plaintext client_secrets may have been written to log output.
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 · scopedUpgrade to provider version 3.0.0, immediately rotate any client_secrets that may have been logged, disable log persistence until patched, and sanitize or remove existing logs that could contain exposed secrets.
Power Platform Terraform Provider version 3.0.0
- Upgrade Power Platform Terraform Provider to version 3.0.0 or later
- Rotate the client_secret for any service principal that has been configured using the affected Terraform provider (versions <= 3.0.0)
- Check if TF_LOG_PATH environment variable was set or if Terraform logs were persisted to file or external systems
- Remove or sanitize any existing logs (on disk, in monitoring systems, or in logging services) that may contain the exposed client_secret
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47083 — 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-2024-47083 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