Emerson OpenBSI through 2022-04-29 mishandles credential storage.

published 2022-08-16 4y ago modified 2026-06-17 4mo ago also EUVD-2022-34266

cvss: 5.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

emerson openbsi 5.9

Is CVE-2022-29959 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-221-03 updated 2022-08-09 cvss 9.6

Emerson OpenBSI

Emerson OpenBSI <= 5.9 SP3
affected: vendor fix, mitigation “Take backups of the information from the SecUsers.ini file securely if the tool has already been used.”

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

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Classification

Weakness

CWE-522 Insufficiently Protected Credentials

References

forescout.com /blog/
third-party-advisory
cisa.gov /uscert/ics/advisories/icsa-22-221-03
mitigation, third-party-advisory, us-government-resource

Sources

CVE List CVE-2022-29959
NVD CVE-2022-29959

Fencer Intel 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.