dbcve.org
Bentley Nevada 3500 System 1 6.x \(3060\/00\) FirmwareOperating system · Bakerhughes

CVE-2021-32997

HIGH · 7.5 CVSS v3.1 Published 2022-05-25
Fix available
A fix is available. Upgrade to 21.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 Baker Hughes Bentley Nevada products (3500 System 1 6.x, Part No. 3060/00 versions 6.98 and prior, 3500 System 1, Part No. 3071/xx & 3072/xx versions 21.1 HF1 and prior, 3500 Rack Configuration, Part No. 129133-01 versions 6.4 and prior, and 3500/22M Firmware, Part No. 288055-01 versions 5.05 and prior) utilize a weak encryption algorithm for storage and transmission of sensitive data, which may allow an attacker to more easily obtain credentials used for access.

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 · moderate confidence

Multiple Baker Hughes Bentley Nevada 3500 monitoring system products (3500 System 1, Rack Configuration, and 3500/22M Firmware) use weak encryption algorithms for storing and transmitting sensitive data including credentials, potentially allowing attackers to recover authentication materials.

MitigationUpdate affected products to versions beyond 6.98, 21.1 HF1, 6.4, and 5.05 respectively; replace weak encryption with strong cryptographic algorithms (AES-256 or equivalent); rotate all credentials after patching.

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
Bentley Nevada 3500 System 1 6.x \(3060\/00\) FirmwareOperating system
Affected:<= 6.98
Bentley Nevada 3500 System 1 \(3072\/xx\) FirmwareOperating system
Affected:< 21.1= 21.1
Bentley Nevada 3500 System 1 \(3071\/xx\) FirmwareOperating system
Affected:< 21.1= 21.1
Bentley Nevada 3500\/22m \(288055 01\) FirmwareOperating system
Affected:<= 5.05
Bentley Nevada 3500 Rack Configuration \(129133 01\) FirmwareOperating system
Affected:<= 6.4

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 the specific 3500 product model
    Locate the product label, system documentation, or access the device web interface to determine if you have a 3500 System 1 (3060/00, 3071/xx, or 3072/xx), 3500/22m (288055 01), or 3500 Rack Configuration (129133 01)
    Affected if The model number matches any of the affected product identifiers listed in the CVE
  2. Determine the installed firmware version
    Access the device configuration interface, system utilities, or consult the system documentation to retrieve the current firmware version number
    Affected if The installed firmware version cannot be determined or is not accessible for verification
  3. Compare version 3500 System 1 (3060/00) against affected range
    If your product is 3500 System 1 6.x with firmware identifier 3060/00, compare your firmware version to <= 6.98
    Affected if Your firmware version is 6.98 or lower
  4. Compare version 3500 System 1 (3072/xx) against affected range
    If your product is 3500 System 1 with firmware identifier 3072/xx, compare your firmware version to < 21.1 or equal to 21.1
    Affected if Your firmware version is lower than 21.1 or exactly 21.1
  5. Compare version 3500 System 1 (3071/xx) against affected range
    If your product is 3500 System 1 with firmware identifier 3071/xx, compare your firmware version to < 21.1 or equal to 21.1
    Affected if Your firmware version is lower than 21.1 or exactly 21.1
  6. Compare 3500/22m and Rack Configuration versions against affected ranges
    For 3500/22m (288055 01) check if version <= 5.05; for 3500 Rack Configuration (129133 01) check if version <= 6.4
    Affected if Your 3500/22m firmware is 5.05 or lower, or your Rack Configuration firmware is 6.4 or lower

You are affected if your product model matches one of the affected identifiers AND your installed firmware version falls within the corresponding vulnerable range.

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 21.1 or later
Fixed in 21.1
Interim mitigation

Update affected products to versions beyond 6.98, 21.1 HF1, 6.4, and 5.05 respectively; replace weak encryption with strong cryptographic algorithms (AES-256 or equivalent); rotate all credentials after patching.

Fix this in Bentley Nevada 3500 System 1 6.x \(3060\/00\) Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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