dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2025-33014

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-18
Fix available
A fix is available. Upgrade to 6.1.2.7_1 / 6.2.0.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 B2B Integrator and IBM Sterling File Gateway 6.0.0.0 through 6.1.2.7 and 6.2.0.0 through 6.2.0.4 uses a web link with untrusted references to an external site. A remote attacker could exploit this vulnerability to expose sensitive information or perform unauthorized actions on the victims’ web browser.

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 Sterling B2B Integrator and Sterling File Gateway contain an open redirect vulnerability where the products use web links with untrusted external references. A remote attacker could craft malicious URLs to redirect victims to arbitrary external sites, potentially enabling phishing attacks or unauthorized actions in the victim's browser session.

MitigationImplement strict URL validation and allowlisting to ensure all redirect links reference only trusted, internal domains. Consider implementing a warning page before any external redirect occurs.

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 B2b IntegratorApplication
Affected:>= 6.0.0.0, < 6.1.2.7_1>= 6.2, < 6.2.0.5
Sterling File GatewayApplication
Affected:>= 6.0.0.0, < 6.1.2.7_1>= 6.2.0.0, < 6.2.0.5

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 product and version
    Locate the IBM Sterling B2B Integrator or Sterling File Gateway installation directory and check the version file or about page within the product web interface
    Affected if The installed version falls within the affected ranges: 6.0.0.0 to 6.1.2.7_0 (exclusive of 6.1.2.7_1), or 6.2.x to 6.2.0.4 (exclusive of 6.2.0.5)
  2. Confirm the web interface is enabled
    Verify the Sterling web application is accessible and running by accessing the product login URL or checking the web service ports in the server configuration
    Affected if The web interface is exposed and accessible, as the open redirect vulnerability exists in web-based URL handling components
  3. Identify URLs with redirect or return parameters
    Review application URLs for parameters commonly used in redirects such as 'redirect', 'returnUrl', 'url', 'target', 'dest', or similar query string parameters that control navigation flow
    Affected if The application uses any GET parameters to specify redirect destinations without strict validation
  4. Test for unvalidated external redirects
    If redirect parameters are identified, craft a test URL with an external domain in the parameter value (for example: https://yourserver/app?redirect=https://malicious.example.com) and observe if the application accepts and follows the external URL
    Affected if The application accepts and redirects to external domains not on an approved allowlist, confirming the open redirect vulnerability exists

A user is affected if the installed IBM Sterling B2B Integrator or Sterling File Gateway version is within the affected ranges AND the web interface is accessible with URL parameters that allow unvalidated external redirect targets.

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 6.1.2.7_1 / 6.2.0.5 or later
Fixed in 6.1.2.7_16.2.0.5
Interim mitigation

Implement strict URL validation and allowlisting to ensure all redirect links reference only trusted, internal domains. Consider implementing a warning page before any external redirect occurs.

Recommended fix High confidence

6.1.2.7_1 (for 6.0.x-6.1.x) or 6.2.0.5 (for 6.2.x)

  1. Determine current version of IBM Sterling B2B Integrator or Sterling File Gateway by checking the system configuration or about page
  2. If running version 6.0.0.0 through 6.1.2.7, upgrade to version 6.1.2.7_1
  3. If running version 6.2.0.0 through 6.2.0.4, upgrade to version 6.2.0.5
  4. After upgrade, verify the system is functioning correctly and test that the URL redirection vulnerability is resolved
  5. Consult IBM Sterling B2B Integrator or Sterling File Gateway documentation for specific upgrade procedures and prerequisites
Caveat Review IBM release notes for upgrade prerequisites and any compatibility considerations before performing the upgrade

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

Fix this in Sterling B2b Integrator Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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 locally
dbcve dependency scanner

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