|
| 1 | +# Bitnami Images |
| 2 | + |
| 3 | +!!! warning "EXPERIMENTAL" |
| 4 | + Scanning results may be inaccurate. |
| 5 | + |
| 6 | +While it is not an OS, this page describes the details of the [container images provided by Bitnami](https://github.com/bitnami/containers). |
| 7 | +Bitnami images are based on [Debian](debian.md). |
| 8 | +Please see [the Debian page](debian.md) for OS packages. |
| 9 | + |
| 10 | +Trivy supports the following scanners for Bitnami packages. |
| 11 | + |
| 12 | +| Scanner | Supported | |
| 13 | +| :-----------: | :-------: | |
| 14 | +| SBOM | ✓ | |
| 15 | +| Vulnerability | ✓ | |
| 16 | +| License | ✓ | |
| 17 | + |
| 18 | +The table below outlines the features offered by Trivy. |
| 19 | + |
| 20 | +| Feature | Supported | |
| 21 | +| :----------------------------------: | :-------: | |
| 22 | +| Unfixed vulnerabilities | - | |
| 23 | +| [Dependency graph][dependency-graph] | - | |
| 24 | + |
| 25 | +## SBOM |
| 26 | +Trivy analyzes the SBOM information contained within the container images provided by Bitnami. |
| 27 | +The SBOM files are located at `/opt/bitnami/<component>/.spdx-<component>.spdx`. |
| 28 | + |
| 29 | +## Vulnerability |
| 30 | +Since Bitnami has its [own vulnerability database][vulndb], it uses these for vulnerability detection of applications and packages distributed by Bitnami. |
| 31 | + |
| 32 | +!!! note |
| 33 | + Trivy does not support vulnerability detection of independently compiled binaries, so even if you scan container images like `nginx:1.15.2`, vulnerabilities in Nginx cannot be detected. |
| 34 | + This is because main applications like Nginx are [not installed by the package manager](https://github.com/nginxinc/docker-nginx/blob/321a13a966eeff945196ddd31a629dad2aa85eda/mainline/debian/Dockerfile). |
| 35 | + However, in the case of Bitnami images, since these SBOMs are stored within the image, scanning `bitnami/nginx:1.15.2` allows for the detection of vulnerabilities in Nginx. |
| 36 | + |
| 37 | +### Fixed Version |
| 38 | +Trivy refers to the [Bitnami database][vulndb]. Please note that these may differ from the upstream fixed versions. |
| 39 | + |
| 40 | +### Severity |
| 41 | +Similar to Fixed versions, it follows Bitnami's vulnerability database. |
| 42 | + |
| 43 | +### Status |
| 44 | +Trivy supports the following [vulnerability statuses] for Bitnami packages. |
| 45 | + |
| 46 | +| Status | Supported | |
| 47 | +| :-----------------: | :-------: | |
| 48 | +| Fixed | ✓ | |
| 49 | +| Affected | ✓ | |
| 50 | +| Under Investigation | | |
| 51 | +| Will Not Fix | | |
| 52 | +| Fix Deferred | | |
| 53 | +| End of Life | | |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | +## License |
| 58 | +If licenses are included in the SBOM distributed by Bitnami, they will be used for scanning. |
| 59 | + |
| 60 | +[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies |
| 61 | + |
| 62 | +[vulndb]: https://github.com/bitnami/vulndb |
| 63 | +[vulnerability statuses]: ../../configuration/filtering.md#by-status |
0 commit comments