A critical vulnerability in @hulumi/drift allows unauthenticated attackers to execute unauthorized operations due to insufficient validation of reconciliation inputs.

This flaw is an instance of CWE-345, where the application accepts and processes untrusted execute plans without verifying their authenticity. The vulnerability is exploitable by unauthenticated remote attackers who can inject malicious plans to bypass security controls.

The ability for an unauthenticated attacker to inject malicious execute plans poses a severe risk to the integrity and availability of managed systems. Successful exploitation could lead to unauthorized system changes, potential data loss, or the performance of unsafe operations, justifying the critical CVSS score of 9.8.

Immediate Action: Update the @hulumi/drift package to version 1.3.2 or later to ensure proper provenance validation is enforced.

Proactive Monitoring: Review application and reconciliation logs for unexpected or unauthorized execute plan submissions that deviate from standard deployment patterns.

Compensating Controls: Implement strict network ingress controls to restrict access to the reconciliation endpoints, ensuring only trusted internal services can communicate with the drift management interface.

Public Exploit Available: No (exploit_available: false)

Given the critical nature of this flaw and the potential for total control over reconciliation operations, immediate patching is required. Organizations should prioritize updating to version 1.3.2 or later across all environments to eliminate this attack vector.