Safeguard
Vulnerability Analysis•

CVE-2022-41738: High Auth Flaw in IBM Storage Scale CNSA

CVE-2022-41738 is a high (7.5) authentication flaw letting outside networks reach containers in IBM Storage Scale CNSA 5.1.2.1 to 5.1.7.0. Fix is 5.1.9.1.

Safeguard Security Team
3 min read

CVE-2022-41738 is a high severity (CVSS 7.5) authentication flaw in IBM Storage Scale Container Native Storage Access, versions 5.1.2.1 through 5.1.7.0. An attacker could initiate connections to containers from external networks. IBM's fix is version 5.1.9.1 or later, followed by the network policy steps in its bulletin.

What's affected

IBM's security bulletin lists IBM Storage Scale Container Native Storage Access, often shortened to CNSA, versions 5.1.2.1 through 5.1.7.0 as affected. The fix is version 5.1.9.1 or later. The same bulletin covers a companion issue, CVE-2022-41737, which allows a local attacker to initiate connections from a container outside the current namespace and carries a score of 7.1 in IBM's CVSS 3.0 vector.

The record scores CVE-2022-41738 at 7.5 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, and IBM's bulletin gives the same 7.5 using CVSS 3.0. The weakness class is CWE-287 (Improper Authentication).

How to check if you're exposed

CNSA runs on Red Hat OpenShift, so start with the cluster. If you have access to the operator namespace, list the CNSA operator and its version through the OpenShift console or the command line, then compare with the affected range:

oc get csv -A | grep -i scale

If the version falls between 5.1.2.1 and 5.1.7.0, you are in the affected range. Also confirm whether network policies are in place around the CNSA namespaces. IBM's bulletin ties the fix to applying network policies after the upgrade, so a patched version without them leaves you short of the intended state.

What to do now

  1. Find every OpenShift cluster that runs CNSA and note the installed version.
  2. Plan the upgrade to 5.1.9.1 or later, using the supported upgrade paths in IBM's documentation.
  3. After upgrading, apply the post upgrade network policy steps that IBM's bulletin links to.
  4. For new installs, enable network policies using the steps in the IBM documentation.
  5. IBM recommends protecting the whole OpenShift cluster with a firewall. Check that yours is in place and that it does not expose cluster internals to outside networks.

Why it matters

The advisory says the flaw lets an attacker start connections to containers from outside networks. In a container platform, the boundary between the cluster and the outside is the very thing you rely on, and a hole there means services meant only for internal use can be reached from elsewhere. The score reflects a high integrity impact with no privileges needed.

IBM's remediation has two parts: a version upgrade and a set of network policies. That mix matters. Part of the real control lives in cluster configuration, not only in the code, so a scanner that only reads version numbers will not tell you whether you are protected. The record's KEV flag is false and the bulletin does not report exploitation. IBM lists no workaround.

Quick check

Is a firewall enough without upgrading?

IBM recommends firewall protection for the whole cluster, but its stated remediation is the upgrade plus network policies. IBM lists no workarounds.

What is CVE-2022-41737?

A companion issue in the same bulletin, scored 7.1 by IBM, where a local attacker could start connections from a container outside the current namespace.

Sources

Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.