what you don't know can hurt you

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:

April 2019

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

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2019 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close