feat(queries): new queries "Instance Uses Metadata Service IMDSv1" for Terraform/aws, Ansible/aws and CloudFormation/AWS

[cx-ricardo-jesus]

Closes #

Reason for Proposed Changes

• Currently we have no support for the verification of the IMDS version in place.

Proposed Changes

• I followed a similar approach regarding the implementation of the query for the platforms Ansible and Terraform. On both of them, I only used a single policy.
• In this policy is used two helper functions, the first one called is_metadata_service_enabled check's if the metadata service is enabled, i.e., when the field http_endpoint is set to enabled or it's not defined at all, which is the same as having the value enabled set (default's to enabled).
• The verification described above is necessary because if the metadata service is not enabled there is no point in checking the http_tokens field.
• After using the first helper function, it's used the other one, that is called http_tokens_undefined_or_not_required that as the name says, checks if the field http_tokens is not defined or is defined as required. The field http_tokens defines if whether or not the metadata service requires IMDSv2.
• On the implementation for the CloudFormation platform, I made the verifications on the field's for two types of resources AWS::EC2::Instance and AWS:EC2::LaunchTemplate.
• I made the same verifications as the queries implemented for the Ansible and Terraform platforms, but for this case the MetadataOptions block is inside the LaunchTemplateData for the resource of type AWS::EC2::LaunchTemplate.
• For all the queries I provided seven different samples, two negative samples and five positive samples.
• The negative samples, the first one hast the metadata_options block defined with both http_endpoint and http_tokens field's defined with enabled and required repectively.
• The positive samples, have all the variations regarding the values that should return a vulnerable result on http_tokens and http_endpoint fields.

I submit this contribution under the Apache-2.0 license.

[github-actions]

KICS version: v2.1.11

Category Results CRITICAL 0 HIGH 0 MEDIUM 0 LOW 0 INFO 0 TRACE 0 TOTAL 0	Metric Values Files scanned 1 Files parsed 1 Files failed to scan 0 Total executed queries 47 Queries failed to execute 0 Execution time 0

[cx-artur-ribeiro]

Hey Ricardo, everything looks good besides the typos 😄.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
19562607	Triggered	Generic Password	f354763	assets/queries/common/passwords_and_secrets/test/positive53.json	View secret
4266022	Triggered	Generic Password	1117a2d	assets/queries/cloudFormation/aws/amplify_app_basic_auth_config_password_exposed/test/negative7.yaml	View secret
9419039	Triggered	Username Password	1117a2d	assets/queries/cloudFormation/aws/amplify_app_basic_auth_config_password_exposed/test/positive6.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[cx-artur-ribeiro]

LGTM, nice job.