←back to thread

219 points mmoogle | 2 comments | | HN request time: 0.455s | source
Show context
moorow ◴[] No.44611680[source]
Bitnami images have been problematic for a little while, especially given their core focus on security but still resulting in a CVE 9.4 in PgPool recently that ended up being used in the underlying infrastructure for a bunch of cloud hosts:

[pgpool] Unauthenticated access to postgres through pgpool · Advisory · bitnami/charts https://share.google/JcgDCtktG8dE2TZY8

replies(1): >>44613238 #
1. carrodher ◴[] No.44613238[source]
That's what Bitnami Secure Images comes to solve. Bitnami regularly updates its images with the latest system packages; however, certain CVEs may persist until they are patched in the OS (Debian 12) or the application itself. Additionally, some CVEs remain unfixed due to the absence of available patches. In vulnerability scanners like Trivy, you can use the `--ignore-unfixed` flag to ignore such CVEs.

In the case of Bitnami Secure Image, the underlying distro is PhotonOS, which is oriented to have zero CVEs.

replies(1): >>44613897 #
2. moorow ◴[] No.44613897[source]
I mean I understand that's the goal, but in this specific CVE it looks like the issue was introduced in Bitnami's own scripts sitting on top of everything, so a ideally-zero-CVE underlying OS isn't going to solve that problem at all.

It also seems like this set of changes was made in this specific way to forcibly disrupt anyone using the existing images, many of which were made off the backs of previously existing non-bitnami open source projects, so I assume you can understand why people are annoyed.

But again, anyone with any knowledge or experience of Broadcom saw this coming, so...