MongoDB Atlas Kubernetes Operator 1.5.0
Approved changes feed: RSS · Atom
cpe:2.3:a:mongodb:atlas_kubernetes_operator:1.5.0:*:*:*:*:*:*:*
part: a version: 1.5.0 update: *
| Vendor | Mongodb (1aa156a6-63a9-5032-baaf-10197d408a1e) |
|---|---|
| Product | Atlas Kubernetes Operator (16b64c70-3487-5471-9e24-a2024ebd507b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/mongodb/mongodb-atlas-kubernetes |
purl2cpe | 2026-06-01 10:11:17.263800 |
pkg:golang/github.com/mongodb/mongodb-atlas-kubernetes |
purl2cpe | 2026-06-01 10:11:17.263801 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-0436 |
vulnerable | 2026-06-03 14:48:46.307993 |
Secret logging may occur in debug mode of Atlas Operator
MEDIUM (4.5)
The affected versions of MongoDB Atlas Kubernetes Operator may print sensitive information like GCP service account keys and API integration secrets while DEBUG mode logging is enabled. This issue affects MongoDB Atlas Kubernetes Operator versions: 1.5.0, 1.6.0, 1.6.1, 1.7.0.
Please note that this is reported on an EOL version of the product, and users are advised to upgrade to the latest supported version.
Required Configuration:
DEBUG logging is not enabled by default, and must be configured by the end-user. To check the log-level of the Operator, review the flags passed in your deployment configuration (eg. https://github.com/mongodb/mongodb-atlas-kubernetes/blob/main/config/manager/manager.yaml#L27 https://github.com/mongodb/mongodb-atlas-kubernetes/blob/main/config/manager/manager.yaml#L27 )
Published: 2023-11-07T11:44:47.971Z
Updated: 2024-08-02T05:10:56.307Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.