CVE-2023-34441 json
Baker Hughes Bently Nevada 3500 System Cleartext Transmission of Sensitive Information
published 2023-10-18 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-38517
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
Baker Hughes – Bently Nevada 3500 System TDI Firmware version 5.05
contains a cleartext transmission vulnerability which could allow an attacker to
steal the authentication secret from communication traffic to the device and reuse it for arbitrary requests.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-23-269-05 updated cvss 6.8
Baker Hughes Bently Nevada 3500
-
Baker Hughes - Bently Nevada Bently Nevada 3500 Rack (TDI Firmware) 5.05affected: mitigation “For customers that do not have access to Baker Hughes DAM may send an email tobentlysupport@bakerhughes.com to request document 106M9733.” dam.bakerhughes.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L |
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
Affected products
- Baker Hughes - Bently Nevada Bently Nevada 3500 System
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
cisa.gov
/news-events/ics-advisories/icsa-23-269-05
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2023-34441
- NVD CVE-2023-34441
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.