Cyber Resilience

CVE-2025-14483

Info Disclosure in Ibm Sterling B2B Integrator 6.1.0.0 – 6.1.2.8

Published
13 March 2026
Modified
20 March 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0024 15th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-14483 is a medium-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability in Ibm Sterling B2B Integrator. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Sterling B2B Integrator 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 disclose sensitive host information to authenticated users in responses that could be used in further attacks against the system.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-36135Same product: Ibm Sterling B2B Integrator
CVE-2023-40693Same product: Ibm Sterling B2B Integrator
CVE-2025-14504Same product: Ibm Sterling B2B Integrator
CVE-2025-2667Same product: Ibm Sterling B2B Integrator
CVE-2025-36134Same product: Ibm Sterling B2B Integrator
CVE-2026-1264Same product: Ibm Sterling B2B Integrator
CVE-2026-0835Same product: Ibm Sterling B2B Integrator
CVE-2025-14031Same product: Ibm Sterling B2B Integrator
CVE-2025-36348Same product: Ibm Sterling B2B Integrator
CVE-2025-36112Same product: Ibm Sterling B2B Integrator

Affected Assets

ibm
sterling b2b integrator
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
ibm
sterling file gateway
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

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-4 Information Flow Enforcement
  • SI-15 Information Output Filtering
Detect
Catch it (NIST detect / respond)
  • AU-13 Monitoring for Information Disclosure
Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V14.2.3

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces policy on what sensitive host data may be included in application responses sent to authenticated users.

prevent

Filters outbound responses to remove or mask sensitive host information before it reaches users.

detect

Monitors application outputs specifically for unintended disclosure of sensitive host data.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.

DE.CM-09 partial match
prevents

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

PR.DS-02 partial match
prevents

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

PR.DS-10 partial match
prevents

Protecting data-in-use includes removing confidential values before they are processed or sent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.

mitigates

Classification identifies sensitive data so it is not inadvertently transmitted.

mitigates

Labelling makes sensitive data visible to developers and prevents accidental inclusion in outbound messages.

mitigates

Information-transfer rules directly govern what data may be sent to external parties.

mitigates

PII-protection requirements reduce the chance of sending personal data to unauthorized recipients.

mitigates

DLP controls inspect and block outbound flows that contain sensitive information.

References