Detecting application vulnerabilities in container images
For the Container Registry integration, the feature is supported for Node, Ruby, PHP, Python, Go binaries and Java. For the CLI and Kubernetes, the feature is supported for Node, Golang, and Java.
Snyk allows detection of vulnerabilities in your application dependencies from container images, as well as from the operating system, all in one single scan.
After you integrate with a container registry and import your projects, we scan your image and test for vulnerabilities.

Enable application vulnerabilities scan from container images

  1. 1.
    Navigate to your container registry integration settings
  2. 2.
    Enable the Detect application vulnerabilities capability and save the changes:
When scanning an image using a container registry, Kubernetes integration, or through the Docker scan command, the scan also uses the --app-vulns flag by default. You are able to opt out of the flag in the container registry only. Do so by disabling the ‘detect application vulnerabilities’ toggle in the integration settings.

Using CLI to detect vulnerabilities

App Vulns Flag

Use the --app-vulns flag to detect vulnerabilities in your application dependencies from container images.
For Java, when specifying the flag, we scan one level of nested jars by default.

Nested Jars Depth Flag

For Java applications, when using --app-vulns, you can also use the --nested-jars-depth=n flag to set how many levels of nested jars Snyk will unpack. The implicit default is 1. I.e when specifying 2, it means that Snyk unzips jars in jars, 3 means Snyk unzips jars in jars in jars, etc.
Users can use --nested-jar-depth=0 to opt out of any scans they feel are unnecessary.

View vulnerabilities and licensing issues

After the feature is enabled, you can see:
  • Dependency vulnerabilities and licensing issues of manifest files detected in your container image.
  • Vulnerabilities detected in operating system packages.
When an image is imported to Snyk, it appears under its registry record in the Projects view, showing the operating system vulnerabilities found in your image.
With this feature enabled, you can also see nested manifest files detected in the image and their vulnerabilities and licensing issues.

Automated scanning

Snyk scans the image regularly based on your project’s settings, and updates you via email or Slack - based on your configuration - when any new vulnerabilities are identified in both the operating system and application dependencies.
For each project, you can choose the test frequency under its settings (the default is daily testing).
For app projects created for apps found in images that are imported from Container Registry integrations, the app will not be re-imported during recurring tests or manual re-test. Instead, the applications dependencies that were found during the initial image import will be tested for new vulnerabilities.
This means that if new dependencies were introduced in an application within an image, they will not be detected by the recurring tests or manual re-test.
In order to detect new or updated applications within images from container registries, the image will need to be re-imported to snyk.
For apps found in images that are imported from the Kubernetes integration, existing apps will be re-imported, but new apps added to the image will not be imported during recurring tests.
In order to detect new applications within images from Kubernetes, the image will need to be re-imported to snyk.
Supported container registries
This is supported across the following container registries:
Supported Integrations
The supported languages work on the following integrations:
Container Registry
Go Binaries