CVE-2022-29953
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 · uneditedThe Bently Nevada 3700 series of condition monitoring equipment through 2022-04-29 has a maintenance interface on port 4001/TCP with undocumented, hardcoded credentials. An attacker capable of connecting to this interface can thus trivially take over its 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 confidenceThe Bently Nevada 3700 series condition monitoring equipment contains undocumented, hardcoded credentials for a maintenance interface accessible on port 4001/TCP. An attacker with network access to this port can authenticate using these credentials and gain full control of the device functionality.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 3700 series device on the networkPerform a network scan to detect Bakerhughes Bently Nevada 3701/40, 3701/44, 3701/46, or 60m100 devices. Check device identification strings or MAC vendor information if available.Affected if The device is a Bently Nevada 3701/40, 3701/44, 3701/46, or 60m100 condition monitoring unit.
-
Check if port 4001/TCP is exposedPerform a TCP port scan targeting port 4001 on the device IP address. Verify if the maintenance interface port is reachable from network segments that should not have administrative access.Affected if Port 4001/TCP is open and accessible from an untrusted network segment.
-
Determine the firmware versionAccess the device web interface or administrative console if available, and retrieve the firmware version information. Compare the installed version against the affected ranges: 3701/40, 3701/44, 3701/46 versions below 4.1, or any version of 60m100.Affected if Firmware version is below 4.1 on 3701/40, 3701/44, or 3701/46, OR the device is a 60m100 on any firmware version.
-
Verify hardcoded credential presenceAttempt to authenticate to the maintenance interface on port 4001/TCP using the default administrative credentials or test for known hardcoded credential patterns documented in security advisories for this CVE.Affected if Authentication succeeds with undocumented or default credentials on the maintenance interface.
A user is affected if they have a Bently Nevada 3701/40, 3701/44, 3701/46 (firmware < 4.1), or 60m100 (any version) device with port 4001/TCP accessible from an untrusted network, as hardcoded credentials can be used to gain full device control.
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
Immediately restrict network access to port 4001/TCP using firewall rules or network segmentation to prevent unauthorized access. Contact Bently Nevada for firmware updates addressing the hardcoded credentials and implement compensating controls until a patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29953 — 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-29953 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