Vulnerability scanning¶
Wodby scans the container images that your app environments currently run for known vulnerabilities: the images it builds from your code, and the images that come with your stack, such as databases and caches. Each environment's Security tab shows how many vulnerabilities its images have, how many of them already have a fix, and the details for each image. Images are rescanned about once a day while they stay deployed, so newly published vulnerabilities appear without a rebuild.
Vulnerability scanning is available on the Team and Enterprise plans. See Billing.
For the vulnerabilities of your clusters, see Cluster security.
What Wodby scans¶
Wodby scans an image while an enabled app service runs it, which means that the service's current deployment of the image completed. This includes derivatives, such as workers or cron services that run another service's build image. An image that several services run is scanned once.
Wodby scans only images stored in the build's own registry repository: Wodby Registry, or the Docker Hub or Distribution Registry integration the build used. Wodby uses the registry credentials of that integration, and only for that registry.
Wodby also scans the other images your app services run, such as the database, cache or search images that come with the stack, or a custom image you set on a service. Wodby finds them in the environment about once a day and pulls them without credentials, so an image in a private registry shows why it couldn't be scanned. An image that many environments run is scanned once, and every environment shows the same result.
An image can be scanned when:
- its registry is reachable over HTTPS at a public address
- it is no larger than 2 GB, counted as the compressed size of its layers
- it provides a
linux/amd64variant, or it is built for a single Linux platform, such aslinux/arm64 - it is a regular container image, without layers that must be downloaded from another location
- it has no more than 256 layers
Results cover operating system packages and application dependencies, such as Node.js, Python, PHP, Go, or Java packages, that the scanner recognizes in the image. The vulnerability database collects advisories from Linux distributions, language ecosystems, and the National Vulnerability Database.
When scans run¶
Wodby scans a newly deployed build image shortly after its deployment completes. Images that don't come from a build are found within about a day of the environment starting to run them. The first result can take longer when many images are waiting for a scan.
After a successful scan, Wodby rescans the image about every 24 hours while it stays deployed. After a failed scan, Wodby retries automatically.
When a build is no longer deployed, Wodby stops rescanning its images. The build keeps showing the last result.
Vulnerabilities that raise an alert¶
Most images have critical or high vulnerabilities that nobody attacks in practice. Wodby raises an alert only for the vulnerabilities that attackers use or are likely to use, whatever their severity:
Exploited: the vulnerability is in CISA's Known Exploited Vulnerabilities catalog, so it has been used in real attacks.Likely exploited: its EPSS score gives it at least a 10% chance of being exploited in the next 30 days.Tracked by Wodby: a serious vulnerability that Wodby tracks itself in a language runtime or web server, such as PHP, nginx, Ruby, Node.js, Java or .NET. Public vulnerability databases can take days to link these to runtimes built from source, and exploitation scores come later still, so Wodby raises the alert as soon as it finds an affected version.
These vulnerabilities raise the alert on the app environment that runs the image and put its build on the
weekly organization report. An image's report tags them Exploited,
Likely exploited or Tracked by Wodby in its Exploitable column.
Images that come with the stack count toward the alert only when a stack upgrade is available, because upgrading can bring a newer image with fixes. When no upgrade is available, the fix depends on a new image from Wodby or the image's maintainers. Those images still show their results, but don't raise the alert.
Critical and high vulnerabilities that don't raise an alert still appear in the results. Fix them too when you can, but they are less urgent.
Exploitation data comes with the vulnerability database and changes over time, so a vulnerability can start or stop raising an alert at the next daily scan, without a new build. The same applies when Wodby starts tracking a vulnerability. Vulnerabilities that have only a GitHub advisory ID, such as some application dependencies, have no EPSS score: they raise an alert only when they're known to be exploited.
Stack updates that fix vulnerabilities¶
Wodby also checks whether a newer version of a service in your stack fixes vulnerabilities that
raise an alert in the images the stack uses now. It checks each version of the
service that the stack offers, such as PHP 8.3 and 8.4. Such updates are marked in the Service update card on the
stack's Operations tab, with the vulnerabilities each one fixes, and the
weekly organization report lists the stack.
To apply the fix, update the stack services, publish the stack draft if the update created one, and upgrade the app environments that use the stack. Environments keep running the vulnerable images until they're upgraded.
An update is marked once Wodby has scanned the images of both service versions, usually within a day of a new service version. Updates aren't marked for:
- pinned stack services, which don't get service updates
- services whose images come from a private registry
- vulnerabilities that the newer image still has, even in a newer package version
If you use Ignore this version for the update, the service leaves the Service update card, but the stack still
counts the update as a security fix while that version fixes vulnerabilities that raise an alert.
Your own services¶
On the Team and Enterprise plans, Wodby also scans the images of the services your organization owns, such as a custom service. It scans every image the latest revision of the service deploys, for each version the service offers, and rescans them about once a day. Catalog services and external services aren't scanned this way: their images are scanned in the environments and stacks that use them.
Wodby scans these images when they come from a public HTTPS registry on port 443. It scans up to 200 different images
of your organization's own services; images beyond that stay Pending.
Open Services > [Service] > Security to see the report of each image, by version and container. Reports read the
same way as an environment's results. Ignores belong to apps, so they don't apply to a service's
reports.
To fix vulnerabilities that raise an alert, publish a new revision of the service with fixed images, then update the stacks that use it.
Images that the service pulls from a private registry with a registry integration aren't scanned. The tab says so instead of showing results.
Read the results¶
Open Apps > [App] > [Environment] > Security. Every environment has the tab except workspaces. It lists only the
images the environment currently runs.
At the top, Vulnerabilities adds up all of the environment's images:
- the number of vulnerabilities that raise an alert, shown as
exploitable - the number of vulnerabilities for each severity: critical, high, medium, low, negligible, and unknown
- the status, when it is not completed:
Failedwhen the latest scan of any image failed, andPendingwhen an image has not been scanned yet
Waiting for new images adds up, in the same way, the images that come with the stack when no stack upgrade is
available. These don't raise the alert.
Below, select an app service to see the report for its image. Each choice names the app service and the build that produced the image, and the report links to that build. For an image that doesn't come from a build, the choice names the image, and the report says whether a stack upgrade is available or the fix waits for a new image. A derivative that runs another service's image has no entry of its own: its results are under the app service that owns the image. A report shows the image's counts, the number of fixable vulnerabilities, which have a fixed package version available, and the times of the last successful scan and the latest attempt. It also lists the image digest, platform, and the date of the vulnerability database used.
Each vulnerability appears once per image and counts once, even when it affects several packages, such as curl and
libcurl, or the PHP command-line and FastCGI binaries. Its row lists all of them and takes the highest severity and
exploitation level among them. It counts as fixable when any of them has a fix.
For each vulnerability, the report shows:
- the vulnerability ID, such as a CVE or GitHub advisory ID, and related IDs
- the severity
- how likely it is to be exploited:
Exploited,Likely exploitedorTracked by Wodbywhen the vulnerability raises an alert,Unlikelywhen its EPSS chance is below 10%, orUnknownwhen it's neither in the CISA catalog nor scored by EPSS. Hover over the tag for its source and the chance of exploitation. You can filter and sort the report by this column. - the affected packages, their versions and type
- whether a fix is available, and the fixed versions
- a link to the advisory
- the location of each package in the image
A report keeps up to 1,000 vulnerabilities per image, starting with those that raise an alert, then the most severe and fixable ones. The counts always include every vulnerability found.
If a rescan fails, the report keeps showing the results of the last successful scan together with the reason the latest scan failed. Wodby retries automatically.
Ignore a vulnerability¶
Ignore a vulnerability that you have reviewed and accepted, for example one in a package your app never uses.
- Open the environment's Security tab and select the app service.
- Click
Ignorein the vulnerability's row. - Enter a reason if you want to keep one, then click
Ignore.
Wodby ignores that vulnerability, with every package its row lists, in every image of every environment of the app, including later scans. Other apps aren't affected. An ignored vulnerability:
- Shows
Ignoredas its severity. Hover over it to see the real severity and the reason. - Moves to the end of the report. The
Severityfilter'sIgnoredoption shows only ignored vulnerabilities. - Isn't counted in the environment's results or status, doesn't raise an alert, and doesn't put the build on the weekly organization report.
To count it again, click Stop ignoring in its row. Ignoring a vulnerability and taking that back require permission
to modify the app.
When an ignored vulnerability starts raising an alert¶
You may ignore a vulnerability while it doesn't raise an alert, and it may start
raising one later: it's added to CISA's catalog, its EPSS chance reaches 10%, or Wodby starts tracking it. Your ignore
then stops applying, because you accepted the vulnerability before it was known to be dangerous. It counts again and
raises the alert, and an orange Ignored before alert tag appears next to its severity. Hover over the tag to see your
earlier reason.
To keep ignoring it, click Ignore again in its row. The ignore then applies while the vulnerability raises the alert,
and your earlier reason stays unless you enter a new one. A vulnerability that you ignore while it already raises an
alert stays ignored.
Weekly organization report¶
On the Team and Enterprise plans, the weekly organization report lists the builds that are currently deployed and have vulnerabilities that raise an alert. Each entry shows the app environment, the build number, its services, how many of its vulnerabilities raise an alert, its total critical and high counts, and the scan date, and links to the environment's Security tab. Builds whose vulnerabilities don't raise an alert aren't listed, however severe. A report lists up to 30 builds and says how many more there are.
The report also lists the stacks whose service updates fix vulnerabilities that raise an alert. Each entry links to the stack and shows each such service with its current and latest versions and the vulnerabilities the update fixes.
Troubleshooting failed scans¶
| Message | What to do |
|---|---|
| The image was not found in its registry. | The image is missing from the registry, for example because it was deleted there. Build and deploy the app service again. |
| The registry rejected the credentials used to pull the image. | Check that the registry integration's credentials can still pull images from the repository. |
| The image registry could not be reached. | Wodby retries automatically. Check the registry's availability if the error persists. |
| The image registry address is not allowed for scanning. Only public HTTPS registries are supported. | Registries on private networks cannot be scanned. |
| The image format is not supported for scanning. | Images with more than 256 layers or with foreign or remotely hosted layers, and artifacts that are not container images, cannot be scanned. |
| The image does not provide a linux/amd64 variant. | Build the image for linux/amd64, or for a single Linux platform. |
| The image is larger than the 2G scanning limit. | Reduce the image size, for example with a multi-stage build. |
| The scan did not finish within 20m0s. | Wodby retries automatically. Very large images can keep reaching the limit. |
| The vulnerability database is temporarily unavailable. | Wodby retries automatically. No action is needed. |
| The vulnerability scanner is temporarily unavailable. | Wodby retries automatically. No action is needed. |
| The registry integration used by this build is no longer available. | The integration was deleted or is no longer shared with the app's project. Build and deploy with an available registry. |
| The image is no longer available for scanning. | The image was voided or removed while it waited for its scan. No action is needed. |
| The image is not stored in the build's registry repository, so it was not scanned. | The CI pipeline reported an image from another registry or repository. Push images to the repository that Wodby assigns to the build. |
| The vulnerability scanner could not analyze the image. | Wodby retries automatically. Contact support if the error persists. |
Plan changes¶
As soon as a downgrade to the Developer plan is scheduled, Wodby stops scanning and hides results, even though the paid period continues. Upgrading again shows the stored results, and Wodby rescans deployed images.