CVE-2023-42016: IBM Sterling B2B Integrator information disclosure

Published Feb 7, 2024
·
Updated

IBM Sterling B2B Integrator Standard Edition 6.0.0.0 through 6.0.3.8 and 6.1.0.0 through 6.1.2.3 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 265559.

Other sources

IBM Sterling B2B Integrator Standard Edition does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.

IBM

Affected Software

4 affected components
IBM Sterling B2B Integrator<=6.0.0.0 - 6.0.3.8
IBM Sterling B2B Integrator<=6.1.0.0 - 6.1.2.3
IBM Sterling B2B Integrator>=6.0.0.0<=6.0.3.8
IBM Sterling B2B Integrator>=6.1.0.0<=6.1.2.3

Event History

Feb 7, 2024
CVE Published
via IBM·12:00 AM
Feb 9, 2024
CVE Published
via MITRE·01:01 AM
Data Sourced
via MITRE·01:01 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 AM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2023-42016?

CVE-2023-42016 is rated as a high severity vulnerability due to its potential for exploitation involving unauthorized access to session cookies.

2

How do I fix CVE-2023-42016?

To resolve CVE-2023-42016, ensure that the secure attribute is set on authorization tokens and session cookies in IBM Sterling B2B Integrator.

3

What versions of IBM Sterling B2B Integrator are affected by CVE-2023-42016?

CVE-2023-42016 affects IBM Sterling B2B Integrator versions 6.0.0.0 through 6.0.3.8 and 6.1.0.0 through 6.1.2.3.

4

What is the main risk associated with CVE-2023-42016?

The main risk of CVE-2023-42016 is that attackers can potentially capture sensitive cookie values, leading to session hijacking.

5

Is user interaction required for exploiting CVE-2023-42016?

Yes, exploitation of CVE-2023-42016 typically requires user interaction, such as clicking a malicious link.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203