App Connect Enterprise Certified ContainerApplication · Ibm

CVE-2022-22491

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-09

Fix available

A fix is available. Upgrade to after 12.4 or later.

See remediation →

57/100

Remediation priority · Elevated

Zero-click

Official description

NVD · unedited

IBM App Connect Enterprise Certified Container 7.1, 7.2, 8.0, 8.1, 8.2, 9.0, 9.1, 9.2, 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 11.4, 11.5, 11.6, 12.0, 12.1, 12.2, 12.3, and 12.4 operands running in Red Hat OpenShift do not restrict writing to the local filesystem, which may result in exhausting the available storage in a Pod, resulting in that Pod being restarted.

Technical summary

dbcve analysis · high confidence

IBM App Connect Enterprise Certified Container versions 7.1-12.4 running in Red Hat OpenShift do not restrict writing to the local filesystem. An unconstrained application can write excessive data to the pod's local storage, filling the available disk space and causing the Pod to be restarted due to storage exhaustion.

MitigationImplement OpenShift pod filesystem restrictions such as emptyDir size limits, PodSecurityPolicy enforcement, or ResourceQuota to prevent unbounded disk usage. Alternatively, configure the application to write only to designated volumes with controlled capacity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

App Connect Enterprise Certified ContainerApplication

Affected:>= 7.0, <= 12.4

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify IBM App Connect Enterprise deployment in OpenShift

Run 'oc get deployments -A' or 'kubectl get deployments -A' and look for deployments containing 'ibm-app-connect' or 'ace' in the name, or inspect your running pods with 'oc get pods -A' and check container images for IBM App Connect Enterprise patterns

Affected if IBM App Connect Enterprise Certified Container deployment or pod is found running in the OpenShift cluster
Check the installed version of IBM App Connect Enterprise

Run 'oc get deployment <deployment-name> -o jsonpath={.spec.template.spec.containers[].image}' or 'kubectl describe pod <pod-name>' to retrieve the container image, then extract the version from the image tag (for example: image: icp4a/ibm-app-connect-enterprise:12.4.0)

Affected if The version falls within the range >= 7.0 and <= 12.4
Verify the environment is Red Hat OpenShift

Run 'oc cluster-info' or check 'kubectl get nodes' output for OpenShift-specific labels or run 'oc version' to confirm OpenShift client is configured

Affected if The application is running in Red Hat OpenShift (the vulnerability only applies in OpenShift environments)
Check for filesystem storage restrictions on the pod

Run 'oc get pod <pod-name> -o jsonpath={.spec}' to inspect the pod spec for emptyDir volume size limits (emptyDir.sizeLimit), or check for PersistentVolumeClaims with storage limits, or inspect the namespace for ResourceQuota objects with storage constraints

Affected if No emptyDir.sizeLimit is set, no storage limits are defined in PersistentVolumeClaims, or no ResourceQuota with storage restrictions exists for the namespace
Check for PodSecurityPolicy or SecurityContextConstraints

Run 'oc get psp' to list PodSecurityPolicies (if available) or 'oc get scc' to check SecurityContextConstraints, then verify whether filesystem write restrictions are enforced

Affected if No PodSecurityPolicy or SCC restricts ephemeral-storage usage, or no such policy is assigned to the service account running the pod

You are affected if you are running IBM App Connect Enterprise Certified Container version 7.0 through 12.4 in OpenShift without filesystem storage restrictions (such as emptyDir size limits, ResourceQuota, or appropriate PodSecurityPolicy/SCC) on your pods.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.4

Interim mitigation

Implement OpenShift pod filesystem restrictions such as emptyDir size limits, PodSecurityPolicy enforcement, or ResourceQuota to prevent unbounded disk usage. Alternatively, configure the application to write only to designated volumes with controlled capacity.

Recommended fix Moderate confidence

Upgrade to the fixed version of IBM App Connect Enterprise Certified Container (check IBM documentation for the specific version beyond 12.4 that addresses CVE-2022-22491)

Check the current IBM App Connect Enterprise Certified Container version running in your OpenShift cluster using 'oc get deployment' or your container registry
Review IBM's official security bulletin for CVE-2022-22491 at www.ibm.com to identify the specific fixed version for your current release
Plan upgrade to the fixed version, ensuring compatibility with your OpenShift cluster version
Before upgrading, backup your integration solutions and configuration data
Upgrade the IBM App Connect Enterprise Certified Container operand in your OperatorHub-managed installation
Verify the upgraded pod runs successfully and monitor storage usage to confirm the resource limit controls are effective
If immediate upgrade is not possible, implement OpenShift pod resource limits and storage quotas as a temporary mitigation

Caveat Review release notes for your target version to check for any breaking changes in API behavior or configuration that may affect your integration solutions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in App Connect Enterprise Certified Container Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing6.0 h
Review / QA2.0 h

20.0 hours of engineering $3,500

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-22491 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.ibm.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22491 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-22491?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to after 12.4 or later

Severity 5.5 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: App Connect Enterprise Certified Container

Remediation

Need this fixed?

Fix this in App Connect Enterprise Certified Container 20 hrs · Moderate

Typical engagement from $3,500

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-22491 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References