Prepare for v0.29.0 #2323
knqyf263
started this conversation in
Development
Replies: 3 comments 1 reply
-
cc: @AnaisUrlichs |
Beta Was this translation helpful? Give feedback.
0 replies
-
I've removed the disclaimer about the line numbers (from helm and RBAC) since I think it belongs in the documentation and might be TMI in the context of release notes (if you disagree just restore it) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi there 👋 I see that this milestone is due by today, is that still true? Sorry for being a bit impatient, we're looking forward to #2188 🙂 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The release note of v0.29.0
💔 BREAKING CHANGES 💔
Change
trivy k8s
APIIt requires
cluster
orall
for cluster scanning.See here for the detail.
Change to rego input schema for dockerfile custom policies
The rego input schema has changed to fix an issue with stage ordering in the Dockerfile parser.
Before:
After:
🚀 What's new? 🚀
🧇 Extensibility using WebAssembly 🐯
Trivy has a new extensions model that allows you to customize the way vulnerabilities are detected and reported, powered by WebAssembly!
Most vulnerability scanners assume that the existence of a vulnerable package indicates your application is vulnerable, but in many cases the vulnerability may not actually affect your application - depending on the runtime version, middleware configuration, or other environmental conditions. The result is that vulnerability scanners sometimes show false positives.
For example, an application with Spring4Shell vulnerability (CVE-2022-22965) would be actually safe if it used JAR packaging and an old Java 8 version - even though your application depends on a vulnerable version of Spring Framework.
With the new extensibility model, a WebAsssembly module can inject custom detection into scanning results.
The following Trivy module for Spring4Shell detects the Tomcat and Java versions in addition to the version of Spring Framework. The module then lowers the severity because this image doesn't satisfy any of the vulnerability conditions and is not actually affected by this vulnerability.
🌴 Show origins of vulnerable dependencies 🎄
Modern software development relies on the use of third-party libraries. Third-party dependencies also depend on others so a list of dependencies can be represented as a dependency graph. In some cases, vulnerable dependencies are not linked directly, and it requires analyses of the tree. To make this task simpler Trivy can show a dependency origin tree with the
--dependency-tree
flag. This flag is available with the--format table
flag only. It supports only Node.js (package-lock.json) as of v0.29.0.This tree is the reverse of the
npm list
command. However, if you want to resolve a vulnerability in a particular indirect dependency, the reversed tree is useful to know where that dependency comes from and identify which package you actually need to update.🎊 containerd support 🤓
When scanning container images, Trivy will try to use images from local image store before attempting to pull from registry. This local image scanning worked with Docker, and from today, it also works with contained.
ℹ️ Rootless containerd is not yet supported.
⛵ Helm Chart scanning 🗺️
Trivy now supports scanning Helm Charts as directories or tarballs (
tar
,tgz
,tar.gz
).Helm charts are rendered into the Kubernetes manifest files that will be applied and any configuration issues displayed for the manifest that would be used.
ℹ️ Support for injecting values files will be added in future releases.
🖌️ Kubernetes secret scanning 📟
trivy k8s
now finds exposed secrets in container images.🔥 RBAC scanning
Trivy now scans Kubernetes RBAC roles in filesystem and it will identify security issues such as permissive or risky role definitions or other RBAC related security best practices.
Beta Was this translation helpful? Give feedback.
All reactions