CVE-2025-14031
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 · uneditedIBM Sterling B2B Integrator and and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0 could allow an unauthenticated attacker to send a specially crafted request that causes the application to crash.
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 confidenceIBM Sterling B2B Integrator and Sterling File Gateway contain a denial-of-service vulnerability where an unauthenticated attacker can send a specially crafted request causing the application to crash. The vulnerability affects versions 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0.
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>= 6.1.0.0, < 6.1.2.8>= 6.2.0.0, < 6.2.0.5_2>= 6.2.1.0, < 6.2.1.1_2= 6.2.2.0>= 6.1.0.0, < 6.1.2.8>= 6.2.0.0, < 6.2.0.5_2>= 6.2.1.0, < 6.2.1.1_2= 6.2.2.0CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if IBM Sterling B2B Integrator or Sterling File Gateway is installedCheck for the product installation directory, typically under /opt/IBM/ or C:\IBM\ on Windows. Look for directories named 'SterlingB2BIntegrator' or 'SterlingFileGateway'. Alternatively, check running processes for 'SB2Bi' or 'sfg' service names.Affected if Either IBM Sterling B2B Integrator or Sterling File Gateway is present on the system
-
Locate and read the installed version fileIn the installation directory, look for version information in files such as 'version.txt', 'build.info', or in the 'properties/version.properties' file. The product typically stores version data in the 'install_dir/properties' or 'install_dir/bin' directory.Affected if The version cannot be determined from standard version files
-
Compare your installed version against affected rangesCompare the discovered version to the affected ranges: 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, or exactly 6.2.2.0. Any version matching these ranges or falling within them indicates vulnerability.Affected if Installed version falls within 6.1.0.0 to 6.1.2.7_2, 6.2.0.0 to 6.2.0.5_1, 6.2.1.0 to 6.2.1.1_1, or equals 6.2.2.0
-
Determine if the web interface is exposed to untrusted networksReview network configuration and firewall rules to check if the application web port (typically 8443, 9443, or 443 for the admin console) is accessible from outside the trusted network. Since this is an unauthenticated DoS vulnerability, external accessibility is required for exploitation.Affected if The web administration interface is accessible from untrusted or public networks without proper filtering
The environment is affected if IBM Sterling B2B Integrator or Sterling File Gateway is installed with a version matching any of the affected ranges (6.1.0.0-6.1.2.7_2, 6.2.0.0-6.2.0.5_1, 6.2.1.0-6.2.1.1_1, or 6.2.2.0) and the web interface is exposed to untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.1.2.86.2.0.5_26.2.1.1_2
Apply the appropriate IBM fix pack or upgrade to a supported version beyond 6.2.2.0 that addresses this vulnerability. If immediate patching is not possible, consider network-level filtering to limit exposure of the affected interface to untrusted networks.
6.1.2.8 (for 6.1.x), 6.2.0.5_2 (for 6.2.0.x), 6.2.1.1_2 (for 6.2.1.x), or latest 6.2.x beyond 6.2.2.0
- 1. Identify the currently installed version of IBM Sterling B2B Integrator and/or Sterling File Gateway using the system's version information or IBM documentation.
- 2. Determine which release train your current version belongs to (6.1.x, 6.2.0.x, 6.2.1.x, or 6.2.2.0).
- 3. For Sterling B2B Integrator 6.1.0.0 - 6.1.2.7: upgrade to version 6.1.2.8 or later.
- 4. For Sterling B2B Integrator 6.2.0.0 - 6.2.0.5_1: upgrade to version 6.2.0.5_2 or later.
- 5. For Sterling B2B Integrator 6.2.1.0 - 6.2.1.1_1: upgrade to version 6.2.1.1_2 or later.
- 6. For Sterling B2B Integrator 6.2.2.0: upgrade to the latest available version (6.2.3.0 or later if available).
- 7. Apply the same version mapping for Sterling File Gateway installations.
- 8. After upgrade, verify the patch was applied successfully and test that the application functions normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14031 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14031 in production — separate from our analysis above.
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.
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.
- 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