Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checkov does not detect hardcoded connection strings in Bicep appSettingsKeyValuePairs #7017

Open
ibadichi-whitesource opened this issue Feb 16, 2025 · 0 comments

Comments

@ibadichi-whitesource
Copy link

Description:
Checkov does not flag hardcoded connection strings in appSettingsKeyValuePairs when scanning a Bicep file.
This is a security risk because connection strings may be leaked in configuration.

Steps to Reproduce:

  1. Create a main.bicep file with the following snippet:

appSettingsKeyValuePairs: {
AppConfiguration__CCaaSConnectionString: appConfig.listKeys().value[0].connectionString
AppConfiguration__ConnectionString: emsAppConfigConnectionString
FUNCTIONS_EXTENSION_VERSION: '~4'
FUNCTIONS_WORKER_RUNTIME: 'dotnet'
}

  1. Run Checkov against the Bicep file:

checkov --directory . --framework bicep

  1. No security warnings are reported, even though ConnectionString values are hardcoded.

Expected Behavior:
Checkov should flag any hardcoded connection strings in appSettingsKeyValuePairs as a potential

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant