LedgerSMB 1.2.0 finally released, fixes CVE-2006-5589



LedgerSMB 1.2.0 has been released, completing a comprehensive SQL injection audit of the code inherited from SQL-Ledger. Numerous SQL injection issues were fixed. In fact, most fields were not properly quoted and escaped. These problems should affect all known versions of SQL-Ledger as well. The fix was delayed because the scale of the changes made required extensive testing-- these were not trivial changes.

Users are advised to upgrade as soon as possible. However, one should also note that (as we have documented in our manual), user permissions are not yet strictly enforced. Therefore, the current recommendation that database user accounts are used to enforce privilege separation still holds.

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.

Best Wishes,
Chris Travers
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.0.0 and SQL-Ledger 2.6.18 and earler arbitrary code execution
    ... 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. ...
    (Bugtraq)
  • Arbitrary Code Execution in SQL-Ledger and LedgerSMB through redirects
    ... This requires a valid login to exploit and was discovered and brought to the attention of both the SQL-Ledger and LedgerSMB team in November. ... Chris Travers ...
    (Bugtraq)