dbcve.org
Sterling Connect\Application · Ibm

CVE-2025-36064

MEDIUM · 5.9 CVSS v3.1 Published 2025-09-22
Fix available
A fix is available. Upgrade to 3.1.0.23 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Sterling Connect:Express for Microsoft Windows 3.1.0.0 through 3.1.0.22 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials.

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 · high confidence

IBM Sterling Connect:Express for Microsoft Windows versions 3.1.0.0 through 3.1.0.22 contains inadequate account lockout settings that allow a remote attacker to perform unlimited login attempts, enabling credential brute force attacks.

MitigationConfigure appropriate account lockout policies (e.g., lock account after 3-5 failed attempts for 15-30 minutes) in the product's authentication settings to prevent brute force attacks.

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
Sterling Connect\Application
Affected:>= 3.1.0.0, < 3.1.0.23

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/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 the installed version of IBM Sterling Connect:Express
    Check the product's About section, installation directory, or Windows Programs and Features to locate the exact version number
    Affected if The version is 3.1.0.0 through 3.1.0.22 (anything less than 3.1.0.23)
  2. Locate the account lockout or authentication policy configuration
    Access the product's administrative console, configuration files, or Windows Local Security Policy where the product's authentication settings are defined
    Affected if Account lockout policy is not explicitly configured or is set to disabled/unlimited attempts
  3. Verify the account lockout threshold setting
    Inspect the lockout configuration to determine the number of failed login attempts allowed before the account is locked
    Affected if The lockout threshold is set to 0, disabled, or a very high number that effectively allows unlimited attempts
  4. Confirm the lockout duration setting
    Check how long an account remains locked after failed attempts, if at all
    Affected if Lockout duration is set to 0 or indefinite without manual administrator intervention

You are affected if the installed version is 3.1.0.0 through 3.1.0.22 and the account lockout policy is disabled or allows unlimited failed login attempts.

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.

dbcve · scoped
Upgrade available Upgrade to 3.1.0.23 or later
Fixed in 3.1.0.23
Interim mitigation

Configure appropriate account lockout policies (e.g., lock account after 3-5 failed attempts for 15-30 minutes) in the product's authentication settings to prevent brute force attacks.

Recommended fix High confidence

3.1.0.23

  1. 1. Identify the current installed version of IBM Sterling Connect:Express for Microsoft Windows by checking the program properties or using the IBM administration console.
  2. 2. Download IBM Sterling Connect:Express for Microsoft Windows version 3.1.0.23 or later from IBM's official support portal (www.ibm.com).
  3. 3. Review IBM's upgrade documentation for Sterling Connect:Express to understand any prerequisites for the upgrade process.
  4. 4. Back up the current IBM Sterling Connect:Express configuration, including any custom settings and adapter configurations.
  5. 5. Stop all IBM Sterling Connect:Express services and related processes before beginning the upgrade.
  6. 6. Execute the installer for version 3.1.0.23, following the on-screen installation wizard steps.
  7. 7. After installation completes, restart the IBM Sterling Connect:Express services.
  8. 8. Verify the installation was successful by checking that the running version displays as 3.1.0.23 or later in the administration console.

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

Fix this in Sterling Connect\ Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36064 — 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-36064 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