{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-47083 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-47083 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-47083 is a high-severity vulnerability in microsoft terraform-provider-power-platform, published on 25 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-47083 and fix it if it is affected.\n\nWhat it is: CVE-2024-47083 is a high-severity vulnerability in microsoft terraform-provider-power-platform, published on 25 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-47083 in the wild and no public exploit code.\n\nAffected product: microsoft terraform-provider-power-platform. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-47083/ (Markdown: https://insights.sbomify.com/CVE-2024-47083/index.md)","id":"CVE-2024-47083","markdown":"https://insights.sbomify.com/CVE-2024-47083/index.md","name":"CVE-2024-47083","record":{"aliases":["GHSA-7w3w-pjm5-m36c"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Terraform provider","requires_auth":"low_privilege","summary":"Attackers with log access can read exposed client secrets from Power Platform Terraform provider logs, requiring secret rotation and log sanitization.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"power_platform_terraform_provider","vendor":"microsoft"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"Power 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Power Platform Terraform Provider has Improper Masking of Secrets in Logs","id":"CVE-2024-47083","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"CORS origin validation is not performed when the request has a cookie in Gradio","id":"CVE-2024-47084"},"packages":[],"prev":{"headline":"Strawberry GraphQL Cross-Site Request Forgery (CSRF) vulnerability","id":"CVE-2024-47082"},"products":["terraform-provider-power-platform"],"published":"2024-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["microsoft"]},"summary":"Attackers with log access can read exposed client secrets from Power Platform Terraform provider logs, requiring secret rotation and log sanitization.","url":"https://insights.sbomify.com/CVE-2024-47083/"}