Safeguard
Vulnerability Analysis•

CVE-2022-43915: Medium Privilege Flaw in IBM App Connect

CVE-2022-43915 is a medium (6.8) privilege escalation in IBM App Connect Certified Container, where unshare is unrestricted. Upgrade the operator.

Safeguard Security Team
4 min read

CVE-2022-43915 is a medium severity (CVSS 6.8) privilege escalation in IBM App Connect Enterprise Certified Container. The product does not limit calls to unshare in running pods, so a user who can execute commands in a pod could raise their privileges. Upgrade the operator and components to IBM's fixed versions.

What's affected

The record and IBM's bulletin list IBM App Connect Enterprise Certified Container versions 5.0 (LTS), 7.1, 7.2, 8.0 through 8.2, 9.0 through 9.2, 10.0, 10.1, 11.0 through 11.6, 12.0 and 12.1.

IBM's remediation depends on your release stream:

  • Continuous Delivery up to 12.1.0: upgrade the operator to 12.2.0 or higher, with all components at 12.0.12.4-r1 or higher.
  • 12.0 LTS: upgrade the operator to 12.0.3 or higher, with all components at 12.0.12-r3 or higher.
  • 5.0 LTS: upgrade the operator to 5.0.19 or higher, with DesignerAuthoring and IntegrationServer components at 12.0.12.3-r1-lts or higher.

The record scores the issue 6.8 (Medium) with vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N. The class is CWE-732 (Incorrect Permission Assignment for Critical Resource). The record says a user with privileged access to execute commands in a running pod is the one who can do it, while IBM's bulletin says a user with access to execute commands. The difference is small, but it means the starting point is command execution inside a pod.

How to check if you're exposed

List the App Connect operator and the operand versions in your clusters. On OpenShift or Kubernetes with the operator's custom resources installed, start with the operator subscription and the pods:

oc get csv -A | grep -i appconnect
oc get pods -A | grep -i appconnect

Compare the operator version with the fixed versions above for your stream. IBM also requires the components, the operands, to be at the stated levels, so check the image tags of the IntegrationServer and DesignerAuthoring pods, not only the operator.

Then ask who has exec access to those pods. The weakness needs command execution in a running pod, so access control on pod exec is a real part of your exposure.

What to do now

  1. Find every App Connect operator and operand and note the release stream.
  2. Upgrade the operator to the fixed version for your stream, then confirm that the components reach the stated levels.
  3. Review who can run exec into the namespaces where App Connect runs, and remove that access from anyone who does not need it.
  4. Use pod security settings that restrict the calls a container can make, as your cluster platform supports.
  5. Record the new versions in your inventory.

Why it matters

Containers share the host kernel, and a kernel feature called namespaces gives each container its own view of the system. The unshare call lets a process create new namespaces. If a product does not limit that call inside a pod, a user who already has a shell there may be able to use it to climb to higher privileges. IBM describes exactly that: a failure to limit unshare in running pods.

The score is medium because the attacker already needs a foothold with command execution and the complexity is high. That does not make it unimportant. Many container compromises start with a foothold in one pod and then move upward. Limiting dangerous system calls is a standard hardening step, and this CVE is a reminder that it needs to be on by default in the products you deploy. The record's KEV flag is false and the bulletin does not report exploitation.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Does an outside attacker get this for free?

No. The weakness needs someone who can already run commands in a running pod. That is why the score is medium.

Do I need to upgrade the components as well as the operator?

Yes. IBM's remediation names minimum component levels in addition to the operator version.

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.