dbcve.org
BeamApplication · Apache

CVE-2020-1929

HIGH · 7.5 CVSS v3.1 Published 2020-01-15
Fix available
A fix is available. Upgrade to after 2.16.0 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 Apache Beam MongoDB connector in versions 2.10.0 to 2.16.0 has an option to disable SSL trust verification. However this configuration is not respected and the certificate verification disables trust verification in every case. This exclusion also gets registered globally which disables trust checking for any code running in the same JVM.

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 Apache Beam MongoDB connector versions 2.10.0-2.16.0 has a critical flaw where an SSL trust verification configuration option is ignored. Regardless of the intended setting, SSL certificate validation is always disabled, and this insecure configuration registers globally in the JVM, disabling trust checking for all code running in that same JVM instance.

MitigationUpgrade the Apache Beam MongoDB connector to version 2.17.0 or later where the configuration is properly respected. If upgrading is not immediately possible, audit all JVM-based applications for exposure and consider isolating the affected connector in a separate JVM process.

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
BeamApplication
Affected:>= 2.10.0, <= 2.16.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Apache Beam MongoDB connector version
    Inspect your project's dependency management file (pom.xml, build.gradle, requirements.txt) or list the loaded JAR files in your runtime classpath. Search for 'beam' and 'mongodb' related artifacts and note their version numbers.
    Affected if The version falls within 2.10.0 through 2.16.0 inclusive.
  2. Locate MongoDB connection configuration
    Search your codebase and configuration files for MongoDB connection URIs or connection string settings. Look for parameters such as 'mongodb://', 'mongo.uri', or MongoDbConnector configuration classes.
    Affected if A MongoDB connection string or configuration is present in your environment.
  3. Verify SSL/TLS settings in MongoDB connection
    Examine the MongoDB connection string for SSL-related parameters such as 'ssl=true', 'sslRequireSSL', 'tls=true', or any custom SSL trust store configurations being passed to the connector.
    Affected if SSL/TLS is explicitly configured or intended to be configured for the MongoDB connection.
  4. Check JVM-wide SSL context impact
    Review your application architecture to determine if other code (different connectors, HTTP clients, database connections) runs in the same JVM process as the MongoDB connector. List all components sharing the same Java process.
    Affected if Multiple applications or connectors share the same JVM process where the MongoDB connector is loaded.

You are affected if the Apache Beam MongoDB connector version is between 2.10.0 and 2.16.0, you are using MongoDB with SSL configuration, and other code shares the same JVM where the global SSL trust verification would be disabled.

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 2.16.0
Interim mitigation

Upgrade the Apache Beam MongoDB connector to version 2.17.0 or later where the configuration is properly respected. If upgrading is not immediately possible, audit all JVM-based applications for exposure and consider isolating the affected connector in a separate JVM process.

Fix this in Beam Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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