dbcve.org
App Connect Enterprise Certified Containers OperandsApplication · Ibm

CVE-2025-1993

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-09
Fix available
A fix is available. Upgrade to after 12.10.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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.

NVD · unedited
IBM App Connect Enterprise Certified Container 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, 12.4, 12.5, 12.6, 12.7, 12.8, 12.9, and 12.10 DesignerAuthoring instances store their flows in a database that is protected by weaker than expected cryptographic algorithms that could be decrypted by a local user.

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.

dbcve analysis · moderate confidence

IBM App Connect Enterprise DesignerAuthoring instances store integration flow configurations in an embedded database using weaker than expected cryptographic algorithms. A local user with database access could potentially decrypt and read the stored flow data due to inadequate encryption strength or outdated cipher implementation.

MitigationImplement stronger cryptographic algorithms (AES-256 or equivalent) for database encryption and rotate encryption keys. Assess and upgrade the encryption mechanism protecting stored flows.

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

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.

NVD · CPE data
App Connect Enterprise Certified Containers OperandsApplication
Affected:= 12.0.7.0= 12.0.11.1= 12.0.11.2= 12.0.11.3= 12.0.12= 12.0.12.0= 12.0.12.2= 12.0.12.3= 12.0.12.4= 12.0.12.5= 13.0.1.0= 13.0.1.1
App Connect OperatorApplication
Affected:>= 8.1.0, <= 11.6.0>= 12.0.0, <= 12.10.0>= 12.1.0, <= 12.10.0

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.

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

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

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.

dbcve checks

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

  1. Identify IBM App Connect Enterprise version
    Run 'kubectl get operands -A' or check the operator version in your OpenShift/Kubernetes cluster. For container operands, check the image tags or deployment configuration using 'kubectl get deployment -A' and inspect container images.
    Affected if The installed version matches any of these: 12.0.7.0, 12.0.11.1, 12.0.11.2, 12.0.11.3, 12.0.12, 12.0.12.0, 12.0.12.2, 12.0.12.3, 12.0.12.4, 12.0.12.5, 13.0.1.0, 13.0.1.1 (for Certified Containers Operands) OR falls within 8.1.0-11.6.0, 12.0.0-12.10.0, or 12.1.0-12.10.0 (for Operator).
  2. Confirm DesignerAuthoring instance is in use
    Check if a DesignerAuthoring resource or pod exists in the namespace. Run 'kubectl get designerauthoring -A' or inspect pods with labels indicating DesignerAuthoring components.
    Affected if A DesignerAuthoring instance is deployed. This is the specific component storing flow configurations in the embedded database mentioned in the CVE.
  3. Locate the embedded database storing flow configurations
    Identify the database container or persistent volume used by the DesignerAuthoring instance. Check pod specifications for database-related containers (such as Derby or similar) and their mount paths.
    Affected if An embedded database (internal to DesignerAuthoring) is present and stores integration flow configurations.
  4. Inspect database encryption configuration
    Examine configuration files, environment variables, or secrets related to database encryption within the DesignerAuthoring namespace. Look for encryption-related settings in configmaps or secrets.
    Affected if The encryption configuration uses legacy or weak cryptographic algorithms (such as DES, 3DES, or AES-128 with weak modes) rather than AES-256 or stronger ciphers.

You are affected if you are running any IBM App Connect Enterprise version within the listed ranges AND have a DesignerAuthoring instance with an embedded database that uses weaker than AES-256 encryption for stored flow data.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 12.10.0
Interim mitigation

Implement stronger cryptographic algorithms (AES-256 or equivalent) for database encryption and rotate encryption keys. Assess and upgrade the encryption mechanism protecting stored flows.

Fix this in App Connect Enterprise Certified Containers Operands Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1993 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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