Twenty Year Anniversary

PRTG Command Injection

PRTG Command Injection
Posted Jun 27, 2018
Authored by Josh Berry

PRTG versions prior to 18.2.39 suffer from a command execution vulnerability.

tags | exploit
advisories | CVE-2018-9276
MD5 | 67b04fa01d539a4d7c74c577383da5d5

PRTG Command Injection

Change Mirror Download
Bugtraq,

I (Josh Berry) discovered an authenticated command injection vulnerability
in the Demo PowerShell notification script provided by versions of PRTG
Network Monitor prior to 18.2.39. The PowerShell notifications demo script
on versions of the application prior to 18.2.39 do not properly sanitize
input in the Parameter field. The web application provides a security
control around running executables/scripts as part of a notification, but
the demo PowerShell script contains a command injection vulnerability. As a
proof of concept, the following value can be passed in the Parameter
field, resulting in the creation of a test account named pentest:

Test.txt;net user pentest p3nT3st! /add

This bypasses the security control in place for the application. I notified
Paessler AG, the developer of the application, and they have since patched
the issue and assigned a CVE of CVE-2018-9276. Additional details are
provided below:

# Vulnerability Title: PRTG < 18.2.39 Command Injection Vulnerability
# Google Dork: N/A, but more details at:
https://www.codewatch.org/blog/?p=453
# Date: Initial report: 2/14/2018, disclosed on 6/25/2018
# Exploit Author: Josh Berry
# Vendor Homepage: https://www.paessler.com
# Software Link: https://www.paessler.com/download/prtg-download?download=1
# Vulnerable Version Tested: 18.1.37.12158
# Patched Version: 18.2.39
# Tested on: Windows 7 and Windows Server 2012 R2
# CVE : CVE-2018-9276

Outside of patching, a workaround would be to just remove the PowerShell
demo script from the notifications directory found in the documentation:
https://www.paessler.com/manuals/prtg/notifications_settings#program.

Note that exploiting this issue requires authenticated access. The tool
installs with the default credentials of prtgadmin / prtgadmin
(https://kb.paessler.com/en/topic/433-what-s-the-login-name-and-password-for
-the-prtg-web-interface-and-enterprise-console-how-to-change), and it is
common for organizations to leave defaults in place or take time in changing
them based on my penetration testing experience.

Thanks,

Josh Berry, OSCP & GCIA Gold
Project Lead - CodeWatch

Cell 469.831.8543 | josh.berry@codewatch.org | www.codewatch.org

Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

December 2018

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Dec 1st
    11 Files
  • 2
    Dec 2nd
    1 Files
  • 3
    Dec 3rd
    18 Files
  • 4
    Dec 4th
    40 Files
  • 5
    Dec 5th
    16 Files
  • 6
    Dec 6th
    50 Files
  • 7
    Dec 7th
    12 Files
  • 8
    Dec 8th
    1 Files
  • 9
    Dec 9th
    1 Files
  • 10
    Dec 10th
    15 Files
  • 11
    Dec 11th
    30 Files
  • 12
    Dec 12th
    25 Files
  • 13
    Dec 13th
    0 Files
  • 14
    Dec 14th
    0 Files
  • 15
    Dec 15th
    0 Files
  • 16
    Dec 16th
    0 Files
  • 17
    Dec 17th
    0 Files
  • 18
    Dec 18th
    0 Files
  • 19
    Dec 19th
    0 Files
  • 20
    Dec 20th
    0 Files
  • 21
    Dec 21st
    0 Files
  • 22
    Dec 22nd
    0 Files
  • 23
    Dec 23rd
    0 Files
  • 24
    Dec 24th
    0 Files
  • 25
    Dec 25th
    0 Files
  • 26
    Dec 26th
    0 Files
  • 27
    Dec 27th
    0 Files
  • 28
    Dec 28th
    0 Files
  • 29
    Dec 29th
    0 Files
  • 30
    Dec 30th
    0 Files
  • 31
    Dec 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2018 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close