dbcve.org
Mongodb Enterprise Kubernetes OperatorDatabase / datastore · MongoDB

CVE-2020-7922

MEDIUM · 6.5 CVSS v3.1 Published 2020-04-09
Fix available
A fix is available. Upgrade to after 1.4.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
X.509 certificates generated by the MongoDB Enterprise Kubernetes Operator may allow an attacker with access to the Kubernetes cluster improper access to MongoDB instances. Customers who do not use X.509 authentication, and those who do not use the Operator to generate their X.509 certificates are unaffected. This issue affects MongoDB Enterprise Kubernetes Operator version 1.0, MongoDB Enterprise Kubernetes Operator version 1.1, MongoDB Enterprise Kubernetes Operator version 1.2 versions prior to 1.2.4, MongoDB Enterprise Kubernetes Operator version 1.3 versions prior to 1.3.1, 1.2, 1.4 versions prior to 1.4.4.

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

The MongoDB Enterprise Kubernetes Operator versions prior to 1.2.4, 1.3.1, and 1.4.4 generate X.509 certificates with insufficient security controls, potentially allowing an attacker with access to the Kubernetes cluster to gain improper access to MongoDB instances. This only affects deployments using X.509 authentication with operator-generated certificates.

MitigationUpgrade the MongoDB Enterprise Kubernetes Operator to version 1.2.4, 1.3.1, or 1.4.4 or later. For existing deployments, regenerate X.509 certificates using the patched operator to ensure proper security controls are applied.

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
Mongodb Enterprise Kubernetes OperatorDatabase / datastore
Affected:>= 1.2.0, <= 1.2.4>= 1.3.0, <= 1.3.1>= 1.4.0, <= 1.4.4= 1.0= 1.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 the deployed Kubernetes Operator version
    Run `kubectl get deployment mongodb-enterprise-operator -n <namespace> -o jsonpath='{.spec.template.spec.containers[0].image}'` to get the operator image, then extract the version tag
    Affected if The version matches the affected ranges: 1.0, 1.1, 1.2.0-1.2.4, 1.3.0-1.3.1, or 1.4.0-1.4.4
  2. Verify X.509 authentication is enabled
    Inspect the MongoDB custom resource: `kubectl get mongodb <resource-name> -n <namespace> -o jsonpath='{.spec.security.authentication}'`
    Affected if Authentication mode is set to x509 or includes x509 configuration
  3. Confirm operator-generated certificates are in use
    Check the MongoDB resource for certificate configuration: `kubectl get mongodb <resource-name> -n <namespace> -o jsonpath='{.spec.security.certificateKeySecretRef}'` and `kubectl get mongodb <resource-name> -n <namespace> -o jsonpath='{.spec.security.clusterCertificateKeySecretRef}'`
    Affected if These fields reference Kubernetes secrets that were created by the operator rather than pre-existing externally-provided certificates

The environment is affected if the operator version is within the vulnerable range AND X.509 authentication is configured using certificates generated by the operator.

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.

From vendor data
Upgrade available Upgrade to a release after 1.4.4
Interim mitigation

Upgrade the MongoDB Enterprise Kubernetes Operator to version 1.2.4, 1.3.1, or 1.4.4 or later. For existing deployments, regenerate X.509 certificates using the patched operator to ensure proper security controls are applied.

Fix this in Mongodb Enterprise Kubernetes Operator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7922 — 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-2020-7922 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