title: Reflected cross-site scripting vulnerability
            product: IBM Sterling B2B Integrator
 vulnerable version: -
      fixed version: or higher
            or higher
            or higher
         CVE number: CVE-2021-20562
             impact: medium
              found: 2021-02-03
                 by: Sutthiwat Panithansuwan (Office Bangkok)
                     Thongchai Silpavarangkura
                     SEC Consult Vulnerability Lab

                     An integrated part of SEC Consult, an Atos company
                     Europe | Asia | North America



Vendor description:
"IBM® Sterling B2B Integrator helps companies integrate all their complex B2B
and EDI processes across partner communities in a single gateway. It provides a
flexible platform, available on premises or through hybrid cloud, that supports
data transformation and most communication protocols; secures your B2B network
and data; provides certified container support; and achieves high availability
for operations with IBM Sterling Global Mailbox. B2B Integrator enables you to
reduce costs by consolidating on a single platform and automating B2B processes
across enterprises, while providing governance, adherence to standards and
visibility for those processes."


Business recommendation:
SEC Consult recommends updating to the latest version of IBM Sterling B2B

An in-depth security analysis performed by security professionals is highly
advised, as the software may be affected from further security issues.

Vulnerability overview/description:
1) Reflected Cross-Site Scripting (CVE-2021-20562)
A reflected cross-site scripting vulnerability has been identified across
multiple functions in the mailbox component of IBM Sterling B2B Integrator,
which can be exploited under the specific condition of a victim's session.

Proof of concept:
1) Reflected Cross-Site Scripting (CVE-2021-20562)
The "securetoken" parameter of the following scripts is affected by the
reflected cross-site scripting vulnerability:

The exploitation is successful if the "SCI_DLSSO" cookie is valid, and the
"JSESSIONID" cookie of the mailbox is invalid or does not exist. One of the
possible scenarios to meet this condition is proceeding to the following steps:

1. Log in to the dashboard via https://<host>/dashboard/Login to obtain an
"SCI_DLSSO" cookie.

2. Visit the mailbox web page via https://<host>/mailbox, which gets logged
in automatically since the web browser sends the "SCI_DLSSO" cookie from the
step 1 to obtain a "JSESSIONID" cookie of the mailbox (Path=/mailbox/).

3. Log out of the dashboard via https://<host>/dashboard/Logout
The server appears to invalidate both "SCI_DLSSO" cookie in the step 1 and
mailbox's "JSESSIONID" cookie in the step 2.

4. Log in to the dashboard via https://<host>/dashboard/Login again to obtain
a new "SCI_DLSSO" cookie.

5. Visit one of the following attacker-prepared URLs, where the web browser
uses the mailbox's "JSESSIONID" cookie in the step 2 and the "SCI_DLSSO"
cookie in the step 4, as follows:


Vulnerable / tested versions:
The version has been tested. According to the vendor, the following product
versions are affected:
* -
* -
* -

Vendor contact timeline:
2021-02-06: Contacting vendor through HackerOne
2021-02-07: HackerOne: Report is currently under investigation
2021-02-23: Vendor: still investigating the vulnerability
2021-02-24: Status change to "triaged", confirmed that it is a valid vulnerability
            Kindly asking vendor to keep us informed
2021-03-29: Asking for a status update
2021-03-29: Vendor will contact us when the public notice / patch is available
2021-04-16: Vendor is still working on the issue.
2021-06-23: Asking for a status update
2021-06-29: Vendor is still working on the issue.
2021-07-27: Vendor: The issue is fixed in previous releases but not in 6.0 yet,
            which is scheduled for a later date.
2021-10-15: Vendor: all patches are publicly available
2021-11-04: Coordinated release of the security advisory

The vendor provides patches for the affected product versions:
* or higher
* or higher
* or higher

Further information can be found here: