Synopsis
Tenable discovered a cross-site scripting (XSS) vulnerability in the playerConfUrl parameter of the Scorm/Rustici Engine interface /defaultui/player/modern.html page. This XSS vulnerability could be leveraged by an attacker to achieve full account takeover against cloud.scorm.com users, and could affect any other LMS which integrates this page, with varying impact.
The issue appears to occur as a result of the call to loadCode(playerConfigurationurl,false) in /defaultui/src/js/integration/loader.js, as playerConfigurationUrl is user-defined and has no limitations in terms of what domain it loads code from, or what kind of URI it accepts. As a result an attacker could craft a malicious link which loads a malicious javascript file from an external site, or uses a data: uri to pass javascript directly.
Proof of Concept:
As Rustici has fixed these issues, the following proof of concept
https://[app-using-scorm]/[path-to-scorm-files]/defaultui/player/modern.html?playerConfUrl=data:text,alert(document.domain)//
Solution
Update to SCORM engine 20.1.45.914+ or 21.1.7.219+Additional References
https://support.scorm.com/hc/en-us/articles/6191663599259-Engine-and-Engine-Dispatch-20-1-45-914https://support.scorm.com/hc/en-us/articles/4899839680155-Engine-and-Engine-Dispatch-21-1-7-219
Disclosure Timeline
All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.
Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.
For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.
If you have questions or corrections about this advisory, please email [email protected]
Contact our sales team