# CVE-2022-29953: Hardcoded credentials in n/a

> Attackers can use hardcoded credentials to take over the maintenance interface of Bently Nevada condition monitoring equipment.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-q25f-hc6j-2jpw

## What is CVE-2022-29953?

CVE-2022-29953 is a critical vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-29953?

It affects 4 products.


Products: Bakerhughes Bently Nevada 3701\/40 Firmware, Bakerhughes Bently Nevada 3701\/44 Firmware, Bakerhughes Bently Nevada 3701\/46 Firmware, Bakerhughes Bently Nevada 60m100 Firmware.

## How do I fix CVE-2022-29953?

No fix has been published for CVE-2022-29953 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-29953 being exploited?

There is no known exploitation of CVE-2022-29953 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-29952](https://insights.sbomify.com/CVE-2022-29952/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29953 and fix it if it is affected.

What it is: CVE-2022-29953 is a critical vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29953 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-29953/ (Markdown: https://insights.sbomify.com/CVE-2022-29953/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-29953
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-29953
- OSV: https://osv.dev/vulnerability/CVE-2022-29953

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-29953/
Summaries are generated and may contain mistakes; the official description above is the record.