
Cloud Vulnerability DB
A community-led vulnerabilities database
Kule masks the secrets a person keeps in the settings files a task's commands can read (the copy's .env files, and .zshrc, .profile, ~/.env and the like in the home layer). A kept secret was replaced only where it was the whole value of a KEY=value setting; inside a line (an alias, a longer value, a command, a comment, or URL/JSON-encoded) the agent could read it. Secrets kept for another folder were not masked in the home layer at all.
Every kept secret, for this folder or another, is masked wherever it is in those files. A commit or an apply puts a masked line back only where it is unchanged, and no more times than the file held it.
Until the fixed release, keep secrets in those files only as a whole KEY=value setting.
Source: NVD
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."