CVE-2023-36857
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 · uneditedBaker Hughes – Bently Nevada 3500 System TDI Firmware version 5.05 contains a replay vulnerability which could allow an attacker to replay older captured packets of traffic to the device to gain 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 confidenceA replay vulnerability in the Bently Nevada 3500 System TDI Firmware v5.05 allows attackers to capture and replay previously recorded network packets to authenticate to the device. The device lacks adequate packet freshness validation (such as sequence numbers, timestamps, or challenge-response mechanisms), enabling authentication bypass through replay of valid but stale traffic.
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= 5.0.5CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Bently Nevada 3500 System presenceLocate any Bently Nevada 3500 System monitors or TDI (Transient Data Interface) modules on the network or in asset inventories. Check ICS/SCADA equipment lists for this specific model.Affected if The target environment contains any Bently Nevada 3500 System hardware with TDI firmware.
-
Determine firmware versionAccess the TDI module web interface or console and retrieve the firmware version from the system information or status page. Alternatively, consult the device documentation or asset management database for the installed firmware version.Affected if The installed firmware version is 5.0.5 (also written as v5.05).
-
Verify network accessibilityCheck if the TDI module management interface (typically Ethernet-based) is reachable from network segments outside the isolated ICS zone. Use network scans or firewall logs to identify exposed management ports.Affected if The device management interface is accessible from corporate or external networks, increasing exposure to replay attacks.
-
Confirm lack of replay protectionInspect the device authentication configuration for any sequence number tracking, timestamp validation, or challenge-response mechanisms. Since CVE-2023-36857 indicates these are absent in v5.0.5, verify the absence in the security settings or authentication logs.Affected if The device lacks packet freshness validation mechanisms such as sequence numbers, timestamps, or challenge-response in its authentication flow.
-
Review authentication logs for replay indicatorsExamine authentication and access logs for duplicate session tokens, identical authentication sequences, or patterns of successful authentications from consistent source patterns that may indicate captured and replayed traffic.Affected if Logs show duplicate or suspiciously timed authentication sequences from the same source credentials.
Your environment is affected if you have a Bently Nevada 3500 System TDI device running firmware version 5.0.5 with its management interface network-accessible and lacking replay attack countermeasures.
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 dataImplement network segmentation to isolate the ICS device, enable packet freshness validation mechanisms if available via firmware update, and consider cryptographic session authentication to prevent replay attacks. Contact Baker Hughes for available firmware patches.
- 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-2023-36857 — 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-2023-36857 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