CVE-2022-29952
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 · uneditedBently Nevada condition monitoring equipment through 2022-04-29 mishandles authentication. It utilizes the TDI command and data protocols (60005/TCP, 60007/TCP) for communications between the monitoring controller and System 1 and/or Bently Nevada Monitor Configuration (BNMC) software. These protocols provide configuration management and historical data related functionality. Neither protocol has any authentication features, allowing any attacker capable of communicating with the ports in question to invoke (a subset of) desired functionality.
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 confidenceBently Nevada condition monitoring equipment uses unauthenticated TDI command and data protocols (60005/TCP, 60007/TCP) for communications between the monitoring controller and System 1/BNMC software. These protocols provide configuration management and historical data functionality but lack any authentication mechanism, allowing any attacker who can reach these ports to invoke desired functionality without credentials.
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< 4.1< 4.1< 4.1all versionsCVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Bently Nevada device modelLocate the physical device label or check network inventory/scanner for Bakerhughes Bently Nevada equipment (model numbers 3701/40, 3701/44, 3701/46, or 60m100). This may also appear in asset inventories or device management interfaces.Affected if The device is one of the following models: 3701/40, 3701/44, 3701/46, or 60m100
-
Check device firmware versionAccess the device web interface, console, or management software (such as System 1/BNMC software) and navigate to the firmware or system information section to retrieve the installed firmware version.Affected if The firmware version is less than 4.1 for models 3701/40, 3701/44, or 3701/46; OR the model is 60m100 (all versions)
-
Verify TDI protocol ports are accessibleUse a network port scanner (such as nmap) to check if ports 60005/TCP and 60007/TCP are open and listening on the device IP address: 'nmap -p 60005,60007 <device_ip>'Affected if Ports 60005/TCP or 60007/TCP are open and reachable from any network segment other than a dedicated management VLAN
-
Assess network exposure of management portsReview firewall rules, ACLs, and network segmentation to determine if ports 60005/TCP and 60007/TCP can be accessed by unauthorized hosts or from untrusted network segments.Affected if The ports are accessible from network segments that contain non-management workstations or untrusted devices
The environment is affected if a Bently Nevada 3701/40, 3701/44, 3701/46 (firmware < 4.1), or 60m100 (any version) device has ports 60005/TCP or 60007/TCP exposed to any network segment beyond authorized management stations.
Generated from the published advisory. Verify against your own configuration.
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 data4.1
Implement network segmentation and firewall rules to restrict access to ports 60005/TCP and 60007/TCP to only authorized management stations. Contact Bently Nevada for firmware/software updates that may address this authentication deficiency.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29952 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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