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

> Attackers can recover user credentials from insecure storage in Emerson OpenBSI, enabling unauthorized access and privilege escalation.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r8mv-jqpq-mx92

## What is CVE-2022-29959?

CVE-2022-29959 is a medium-severity vulnerability in n/a, published on 16 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Emerson OpenBSI through 2022-04-29 mishandles credential storage. It is an engineering environment for the ControlWave and Bristol Babcock line of RTUs. This environment provides access control functionality through user authentication and privilege management. The credentials for various users are stored insecurely in the SecUsers.ini file by using a simple string transformation rather than a cryptographic mechanism.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Emerson Openbsi.

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

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

## Is CVE-2022-29959 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29960](https://insights.sbomify.com/CVE-2022-29960/): Weak cryptography in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29959 is a medium-severity vulnerability in n/a, published on 16 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29959 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-29959/ (Markdown: https://insights.sbomify.com/CVE-2022-29959/index.md)
```

## Sources

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

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