A Looker user with a Developer role could potentially cause Looker to execute a malicious command. This is due to insecure processing of Teradata driver parameters. Both Looker-hosted and Self-hosted instances were found to be affected. The issue has been mitigated for Looker-hosted instances, requiring no user action. The issue involves the processing of parameters within the Teradata driver, potentially allowing for command execution.