what you don't know can hurt you
Home Files News &[SERVICES_TAB]About Contact Add New

lpanelPlain.txt

lpanelPlain.txt
Posted Jun 18, 2005

Lpanel versions 1.59 and below suffer from a cross site scripting flaw in viewticket.php.

tags | exploit, php, xss
SHA-256 | 5e4c07390eccf0934d7ca80e4ea095e742a6c852bdce2142063703df9a77a602

lpanelPlain.txt

Change Mirror Download
Subject:
Lpanel.NET's Lpanel (all versions up to and including 1.59) is vulnerable to plain-text session credential leakage via script injection.


Severity:
High; Full access to all client functions can be obtained with little effort, putting entire installations of the software and its users at risk.


Preamble:
(Taken from http://www.lpanel.net/)
Lpanel is a Complete Web Hosting Billing & Automation Suite that installs over cPanel, WHM.

Created from the ground up from cPanel by web hosting administrators, Lpanel has everything a cPanel hosting business needs and will ever need. Constantly expanding to meet the quickly developing web hosting market, Lpanel is the only complete management solution available today for cPanel web hosts. From multi-staff tiers, automated signups, reseller management, network utilities, automated SSL, as well as a full array of “Added Services” and detailed efficiency reports - Lpanel is always steps ahead of the rest.


Problem:
Lpanel.NET's Lpanel is vulnerable to plain-text credential leakage due to a bug in the use of a GET variable within the system. Using this bug maliciously, an attacker could gain unauthorized access to the plain-text session credentials of other users in the system. The attacker needs absolutely no access to the system to exploit this vulnerability. The targeted variable is the “pid” GET variable, often sent to view_ticket.php (i.e. http://yourdomain.com/lpanel/help/view_ticket.php?pid=50). An attacker can insert malicious URL encoded javascript into the GET variable, and cause view clients to forfeit their session information to javascript. An example malicious URL would be:

http://yourdomain.com/lpanel/help/view_ticket.php?pid=%22%3E%3C%2Ftd%3E%3Cscript+language%3Djavascript%3Ealert%28document.cookie%29%3B%3C%2Fscript%3E

However the above URL does not actually instruct the client's browser to send out the session information, it merely proves the validity of the vulnerability. Thus an attacker could persuade an innocent system user to click the link, and with the appropriate javascript inserted into the URL, have session information forwarded to themselves, thus giving them access to that client's session. Once session information was acquired, the attacker would need simply to insert the user's session information as cookies into their own browser, and hit the installation of Lpanel, thus gaining full unauthorized access to the user's account, credentials, and functions.


Workaround:
This bug can be fixed by securing the “pid” variable before use. An alternative workaround would be to use another vendor, that secures user input. Perhaps this vulnerability would've been caught in the initial stages of development had the product been released open source, making case for one to seek out an open source solution, or at least a solution with a better proven track record. “Lpanel is always steps ahead of the rest.” -- Negative.


Vendor Contact:
Lpanel.NET's Lpanel
URL: http://www.lpanel.net/
Email: sales@lpanel.net (I was unable to find a more relevant email contact)
Mailing Address:
Lpanel.NET
PO Box 940876
Miami, Florida 33194-0056
United States
Phone: 614-441-4838


Disclosure Timeline:
Vendor Notified: June 6, 2005
Public Release: June 6, 2005


About the Author:
The author is in between life paths at the moment, but is currently a software engineer at a company to remain unnamed. When not at his computer, the author enjoys doing a great many things, most of which he has lost all time for, or lacks people to do those things with in his current lifestyle. As such he finds more time for work, or just visits Blockbuster, and when all else fails, fabricates reports such as this.

The author is posting this message anonymously in order to avoid potential legal consequences, although he is having trouble seeing any potential consequences as feasible, considering the vendor does not release a plain-text version of their license (the license is actually encoded, and when viewed, renders a PHP parse error).


Greets:
I'd like to say hi to the team with which I work; you're all great. I'd also like to say hello to swoolley and tautology.

--
Login or Register to add favorites

File Archive:

September 2024

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

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2024 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close