DependencyTrack / DependencyTrack/frontend
How to handle vulnerabilities with available fixes in frontend image
- Dominant language
- Vue
- Stars
- 171
- Forks
- 250
- Avg merge
- 11h 12m
- Merged PRs (30d)
- 82
Description
Hi,
I am using the provided images of DependencyTrack and running a [trivy](https://github.com/aquasecurity/trivy) scan before deploying those.
Sometimes, there are vulnerabilities in the images, which might be fixed by an update && upgrade.
For example:
```
trivy -q image --format table dependencytrack/frontend:4.6.1
dependencytrack/frontend:4.6.1 (alpine 3.16.2)
Total: 8 (UNKNOWN: 0, LOW: 0, MEDIUM: 2, HIGH: 4, CRITICAL: 2)
┌─────────┬────────────────┬──────────┬───────────────────┬───────────────┬────────────────────────────────────────────────────────────┐
│ Library │ Vulnerability │ Severity │ Installed Version │ Fixed Version │ Title │
├─────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
│ curl │ CVE-2022-42915 │ CRITICAL │ 7.83.1-r3 │ 7.83.1-r4 │ curl: HTTP proxy double-free │
│ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2022-42915 │
│ ├────────────────┼──────────┤ │ ├────────────────────────────────────────────────────────────┤
│ │ CVE-2022-42916 │ HIGH │ │ │ curl: HSTS bypass via IDN │
│ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2022-42916 │
│ ├────────────────┼──────────┤ │ ├────────────────────────────────────────────────────────────┤
│ │ CVE-2022-32221 │ MEDIUM │ │ │ curl: POST following PUT confusion │
│ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2022-32221 │
├─────────┼────────────────┼──────────┤ │ ├────────────────────────────────────────────────────────────┤
│ libcurl │ CVE-2022-42915 │ CRITICAL │ │ │ curl: HTTP proxy double-free │
│ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2022-42915 │
│ ├────────────────┼──────────┤ │ ├────────────────────────────────────────────────────────────┤
│ │ CVE-2022-42916 │ HIGH │ │ │ curl: HSTS bypass via IDN │
│ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2022-42916 │
│ ├────────────────┼──────────┤ │ ├────────────────────────────────────────────────────────────┤
│ │ CVE-2022-32221 │ MEDIUM │ │ │ curl: POST following PUT confusion │
│ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2022-32221 │
├─────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
│ libxml2 │ CVE-2022-40303 │ HIGH │ 2.9.14-r1 │ 2.9.14-r2 │ libxml2: integer overflows with XML_PARSE_HUGE │
│ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2022-40303 │
│ ├────────────────┤ │ │ ├────────────────────────────────────────────────────────────┤
│ │ CVE-2022-40304 │ │ │ │ libxml2: dict corruption caused by entity reference cycles │
│ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2022-40304 │
└─────────┴────────────────┴──────────┴───────────────────┴───────────────┴────────────────────────────────────────────────────────────┘
```
These vulnerabilites could be fixed by updating the libraries and I assume that the vulnerabilities are gone with the next release.
But until then, I need to take care of those. I am considering to use the "original" frontend image as base image and update the libraries, for example like this:
```
FROM dependencytrack/frontend:4.6.1
USER root
RUN apk update && apk upgrade
USER nginx
```
But since I assume, that others are also facing this issue, are there any suggestion?
For example, would it be possible to release more frequently, to keep the images up-to-date?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.