LedgerSMB 1.0.0 and SQL-Ledger 2.6.18 and earler arbitrary code execution



Hi all;

Summary:
A directory transversal issue was found in LedgerSMB 1.0.0 involving the terminal variable. This vulnerability was inherited from the SQL-Ledger codebase. Due to the fact that SQL-Ledger has a built-in text editor, this issue could result in arbitrary code execution on the server. The SQL-Ledger and LedgerSMB teams have both released patches to these vulnerabilities.

Software affected:
SQL-Ledger, all versions prior to 2.6.19.
LedgerSMB 1.0.0
Other SQL-Ledger derivatives should presume themselves vulnerable (we have not checked).

Patched versions:
SQL-Ledger 2.6.19
LedgerSMB 1.0.0p1
SQL-Ledger 2.4.4-2.4.17 are particularly vulnerable due to CVE-2006-4244.

Mitigating factors:
Authentication is required (only for LedgerSMB 1.0.0 and SQL-Ledger 2.4.3 and lower, or 2.6.18).

Detailed description:
The "terminal" query variable is insufficiently checked in the login.pl and admin.pl files for validity and can lead to directory transversal and arbitrary code execution in SQL-Ledger (2.6.18 and earlier) and LedgerSMB (1.0.0 only). In particular, an attacker could upload a file called "login.pl" using these facilities. The attacher could then pass a specially malformed url to the web server that would cause it to execute the code. The form of the url might be:
http://hostname/path/login.pl?termina=../css

In the course of our disclosure, we sent a notification to the developer of SQL-Ledger who quickly patched his software.

All customers should upgrade to the newest versions of these packages at their earliest convenience.

Credit for this disclosure should go to Chris Murtagh (a private individual) and Richard Patterson of Quickhelp.

Best Wishes,
Chris Travers
Metatron Technology Consulting
begin:vcard
fn:Chris Travers
n:Travers;Chris
email;internet:chris@xxxxxxxxxxxxxxxx
tel;work:509-888-0220
tel;cell:509-630-7794
x-mozilla-html:FALSE
version:2.1
end:vcard



Relevant Pages

  • Full disclosure: Directory Transversal and Arbitrary Code Execution Vulnerability in SQL-Ledger
    ... Another security issue has been found in LedgerSMB < 1.1.5 and all versions of SQL-Ledger which allows an attacker to engage in directory transversal, retrieval of sensitive information, user account fabrication, or even arbitrary code execution. ... The stripping of such "dangerous" elements involves first stripping the $userpath and then the $memberfile and then opening the file that remains. ... You can also retrieve the memberfile by using the path of file=useuserusers/memberssrs/members. ...
    (Bugtraq)
  • DoS and code execution issue in LedgerSMB < 1.1.5 and SQL-Ledger < 2.6.25
    ... A person on the LedgerSMB core team has found a serious arbitrary code execution issue in LedgerSMB prior to 1.1.5 and SQL-Ledger. ...
    (Bugtraq)
  • ACLS ineffective in SQL-Ledger and LedgerSMB
    ... LedgerSMB is also affected but the problem has been mentioned in our documentation since the fork. ... Ordinarily I would not make a big deal out of this (since we are already clear about why we suggest using db accounts for security), but I feel that DWS is misrepresenting the security of SQL-Ledger and I think people need to be aware of the risk. ... The access control lists associated with users in SQL-Ledger and LedgerSMB do nothing more than enable or disable menu items. ...
    (Bugtraq)
  • LedgerSMB 1.2.0 finally released, fixes CVE-2006-5589
    ... completing a comprehensive SQL injection audit of the code inherited from SQL-Ledger. ... Those who maintain security advisory lists should list CVE-2006-5589 as now officially closed for LedgerSMB, though it is likely to remain open for SQL-Ledger. ... Chris Travers ...
    (Bugtraq)