| Reporter | Title | Published | Views | Family All 18 |
|---|---|---|---|---|
| IBM Sterling B2B Integrator 5.2.0.1/5.2.6.3 - Cross-Site Scripting Vulnerability | 13 Aug 201800:00 | – | zdt | |
| CVE-2018-1513 | 13 Aug 201800:00 | – | circl | |
| CVE-2018-1563 | 13 Aug 201800:00 | – | circl | |
| IBM Sterling B2B Integrator Cross-Site Scripting Vulnerability (CNVD-2018-13986) | 24 Jul 201800:00 | – | cnvd | |
| IBM Sterling B2B Integrator Cross-Site Scripting Vulnerability (CNVD-2018-14086) | 23 Jul 201800:00 | – | cnvd | |
| CVE-2018-1513 | 23 Jul 201813:00 | – | cve | |
| CVE-2018-1563 | 20 Jul 201816:00 | – | cve | |
| CVE-2018-1513 | 23 Jul 201813:00 | – | cvelist | |
| CVE-2018-1563 | 20 Jul 201816:00 | – | cvelist | |
| Security Bulletin: Cross-site Scripting Vulnerability Affects IBM Sterling B2B Integrator Standard Edition (CVE-2018-1563, CVE-2018-1513) | 5 Feb 202000:53 | – | ibm |
# Exploit Title: [IBM Sterling B2B Integrator persistent cross-site scripting]
# Exploit Author: [Vikas Khanna] (https://www.linkedin.com/in/leetvikaskhanna/) (https://twitter.com/MR_SHANU_KHANNA)
# Vendor Homepage: [https://www.ibm.com/support/knowledgecenter/en/SS3JSW_5.2.0/com.ibm.help.overview.doc/si_overview.html]
# Version: [IBM Sterling B2B Integrator 5.2.0.1 - 5.2.6.3] (REQUIRED)
# CVE : [CVE-2018-1513 & CVE-2018-1563]
Vulnerability Details
Vulnerability Name : Persistent Cross Site Scripting
Affected Parameter(s) : fname & lname
Steps to reproduce
Step 1 : Login to the IBM Sterling B2B Integrator.
Step 2 : Navigate to Performance Tuning module, Username will be displayed as below :-
Last Edited By <USERNAME>
Note :- Modify the configuration for example and check the Last Edited By - Username. Any user (Admin or Non admin) who have privileges to change the configuration can act like an attacker.
Step 3 : Navigate to My Account and update first name and last name.
Step 4: Intercept the request using burp suite and insert the <Video><source onerror=”alert(1)”> payload & <Video><source onerror=”alert(2)”> payload in fname and lname parameter.
Step 5 : It has been observed that My account module is not vulnerable to XSS but Performance Tuning tab under Operations -> Performance is vulnerable, as the Performance Tuning tab displays the user’s first name and last name separately as “Last Edited By USERNAME”.
Step 6 : Now navigate to Performance Tuning module. It is seen that the application is vulnerable to Persistent Cross Site Scripting.
Note : It has been observed that any user who has access to Performance Tuning tab will be vulnerable and the same javascript payload will execute for them as well.Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation