update(query): add CWE information to volume_has_sensitive_host_directory

[julianthome]

** Reason for Proposed Changes**

• CWE information for the query was missing

** Proposed Changes**

• Adding 668 as Exposure of Resource to Wrong Sphere seems the best fit covering both confidentiality and integrity concerns.

I submit this contribution under the Apache-2.0 license.

[ArturRibeiro-CX]

Hi @julianthome,
Thanks for your the contribution!
At the moment, the query metadata does not have 2 required fields, which is causing the e2e tests to fail, as you can see in the actions pipeline below.
Can you kindly add oldSeverity and cloudProvider fields to the metadata, like so:

(other query's metadata fields)
"descriptionID": "8361cc0a",
"oldSeverity": "HIGH",
"cloudProvider": "common",
"cwe": "668"
}
As soon as you do, I'll approve the PR.

Best regards.

[julianthome]

Thanks a lot @ArturRibeiro-CX ... would you mind re-checking the update. Are the changes acceptable?

[ArturRibeiro-CX]

Hi @julianthome,
Thanks for you contribution, those changes are enough.
We'll merge this PR as soon as possible.
Best regards.

[gitguardian]

⚠️ GitGuardian has uncovered 6 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
4266030	Triggered	Generic Password	b711135	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266030	Triggered	Generic Password	b711135	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266030	Triggered	Generic Password	b711135	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266030	Triggered	Generic Password	b711135	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266006	Triggered	Generic Password	b711135	assets/queries/common/passwords_and_secrets/test/negative32.yaml	View secret
4266006	Triggered	Generic Password	b711135	assets/queries/common/passwords_and_secrets/test/negative42.yaml	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.}

[ArturRibeiro-CX]

Hi @julianthome,
Just to let you know that your PR was merged today.
Thanks for your contribution to KICS.

Best regards.