SQL-Ledger serious security vulnerability and workaround

Credit: Chris Travers
Risk: High
Local: No
Remote: Yes
CWE: CWE-287

CVSS Base Score: 7.5/10
Impact Subscore: 6.4/10
Exploitability Subscore: 10/10
Exploit range: Remote
Attack complexity: Low
Authentication: No required
Confidentiality impact: Partial
Integrity impact: Partial
Availability impact: Partial

Hi; This post is to inform everyone that there is a serious security hole that has been discovered in SQL-Ledger involving session handling. The flaw allows anyone with network access to the server to access the application as any logged in user using trivial mechanisms. I have previously brought this flaw up with Dieter several months ago, and since it is still an issue, I have sent him a fix that a few of us have prepared. This fix was prepared by myself and Christopher Murtagh with the help of a few testers. In the mean time, we recommend that people take the following precautions: 1) DO NOT allow unauthorized users access to the SQL-Ledger application. Use .htaccess files or network mechanisms to prevent unauthorized access to the application or server. 2) If different departments require different levels of access, move departmental roles into separate applications, and enforce permissions accordingly. The different installations can access the same database, however. Full disclosure will follow two weeks from yesterday. Best Wishes, Chris Travers Metatron Technology Consulting

Vote for this issue:


Thanks for you vote!


Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.

(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2021, cxsecurity.com


Back to Top