A security vulnerability exists in the Sealed Secrets controller's unauthenticated POST endpoints. By submitting a modified payload containing custom Go template logic in spec.template.data, an attacker with internal network access can abuse the handler as a decryption oracle to...
Vendor
Bitnami vulnerabilities
5 published CVES affecting Bitnami, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 1
- High
- 1
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
- sealed-secrets 2
- bitnami/cassandra 1
- bitnami/mariadb-galera 1
- bitnami/mariadb-galera Helm chart 1
- containers 1
Latest Bitnami CVEs
Newest publication first
-
MediumCVSS 4.2 EPSS 0.40%
-
CriticalCVSS 9.8 EPSS 0.48%
Bitnami Cassandra container images are affected by a retained default superuser vulnerability. When a custom administrator account is configured via the CASSANDRA_USER environment variable, the container initialization script creates the new superuser account but fails to drop th...
-
MediumCVSS 5.3 EPSS 0.31%
Bitnami MariaDB Galera container images and Helm chart are affected by a hardcoded default credential vulnerability in the Galera replication health-check user. The MARIADB_REPLICATION_USER and MARIADB_REPLICATION_PASSWORD environment variables defaulted to monitor and monitor re...
-
MediumCVSS 4.9 EPSS 0.41%
Bitnami Sealed Secrets is vulnerable to a scope-widening attack during the secret rotation (/v1/rotate) flow. The rotation handler derives the sealing scope for the newly encrypted output from untrusted spec.template.metadata.annotations present in the input SealedSecret. By subm...
-
HighCVSS 7.3 EPSS 0.65%
In Bitnami Containers, all Laravel container versions prior to: 6.20.0-debian-10-r107 for Laravel 6, 7.30.1-debian-10-r108 for Laravel 7 and 8.5.11-debian-10-r0 for Laravel 8, the file /tmp/app/.env is generated at the time that the docker image bitnami/laravel was built, and the...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.