dbcve.org
Atlas Kubernetes OperatorApplication · MongoDB

CVE-2023-0436

HIGH · 7.5 CVSS v3.1 Published 2023-11-07
Fix available
A fix is available. Upgrade to 1.7.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 )

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MongoDB Atlas Kubernetes Operator versions 1.5.0 through 1.7.0 log sensitive information including GCP service account keys and API integration secrets when DEBUG logging mode is enabled. This creates a credential exposure risk through log file access.

MitigationIf DEBUG logging is enabled, disable it immediately by removing the --zap-log-level=debug flag from the operator deployment. Additionally, upgrade to the latest supported version as this affected version is EOL.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Atlas Kubernetes OperatorApplication
Affected:>= 1.6.0, < 1.7.1= 1.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify MongoDB Atlas Kubernetes Operator deployment
    Run 'kubectl get deployments -A' and look for deployments named 'mongodb-atlas-kubernetes-operator' or similar Atlas-related operators
    Affected if No Atlas operator deployment exists in the cluster, then the system is not affected by this CVE
  2. Check installed operator version
    Run 'kubectl get deployment <atlas-operator-deployment> -o jsonpath={.spec.template.spec.containers[0].image}' in the namespace where the operator is installed, then extract the version tag from the image name (e.g., mongodb/atlas-operator:1.5.0 or 1.7.0)
    Affected if The version is 1.5.0, or between 1.6.0 and 1.7.0 inclusive (1.6.0 <= version < 1.7.1), then the operator is in the affected version range
  3. Verify DEBUG logging is not enabled
    Run 'kubectl get deployment <atlas-operator-deployment> -o jsonpath={.spec.template.spec.containers[0].command}' to check for the --zap-log-level=debug flag in the operator's command arguments
    Affected if The command output contains '--zap-log-level=debug' or '--zap-level=debug', then DEBUG logging is enabled and sensitive data may be logged

The environment is affected only if the MongoDB Atlas Kubernetes Operator version is 1.5.0 or between 1.6.0 and 1.7.0 AND DEBUG logging is currently enabled via the operator deployment flags.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.7.1 or later
Fixed in 1.7.1
Interim mitigation

If DEBUG logging is enabled, disable it immediately by removing the --zap-log-level=debug flag from the operator deployment. Additionally, upgrade to the latest supported version as this affected version is EOL.

Recommended fix High confidence

1.7.1 or later (latest stable release)

  1. Upgrade the MongoDB Atlas Kubernetes Operator to version 1.7.1 or later (preferably the latest stable release)
  2. After upgrading, verify that sensitive information is no longer logged by reviewing your operator logs
  3. If immediate upgrade is not possible, as a temporary mitigation ensure DEBUG logging is disabled in your operator deployment (check the --zap-log-level flag in config/manager/manager.yaml)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Atlas Kubernetes Operator Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0436 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0436 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data