SQL Database Error could lead to SQL Injection with internal Path Disclosure in froxlor/froxlor

Valid

Reported on

Jan 27th 2023


Hello,

Through manipulating Parameter i get an SQL Error which can lead to SQL Injection. Plus that there is an internal Path Disclosure.

Best regards Ahmed Hassan

Impact

Hello,

Through manipulating Parameter i get an SQL Error which can lead to SQL Injection. Plus that there is an internal Path Disclosure.

Best regards Ahmed Hassan

We are processing your report and will contact the froxlor team within 24 hours. 2 months ago
Michael
2 months ago

Maintainer


Can you please explain where an actual SQL Injection is possible? All i see is a failed prepared SQL query

ahmedvienna
2 months ago

Researcher


As i mentioned it is possible to find a SQL Injection Vulnerability but i did not mention that i find a SQL Injection Vulnerability.

Due to this Error the attacker can try different Syntax to identify the columns and number, names of the tables used.

Moreover failing to use a prepared statement/query can be a big issue for a SQL Injection Vulnerability due to no prepared statements given from the Devekoper and the Code will run in the Database and interpreted as Code.

Plus that you can see the Error Message coming out at the End of the Video. This should also be not visible for normal Users.

Michael
2 months ago

Maintainer


You've specified this report type to be CWE-89: SQL Injection - which is just untrue. Froxlor uses prepared statements throughout the system.

The uncaught exception has been fixed. Also keep in mind that our demo has special adjustments and might not always reflect 100% the same as the current release.

ahmedvienna
2 months ago

Researcher


Thats good to know so you patched the uncaught Error which was the main problem and security Issue with the internal Path Disclosure.

I will be happy if you can verify the security issue as you have patched the uncaught exception as mentioned before.

ahmedvienna modified the report
2 months ago
ahmedvienna
2 months ago

Researcher


The Vulnerability Report Title was changed as its is not a SQL Injection Vulnerability.

ahmedvienna modified the report
2 months ago
Michael Kaufmann validated this vulnerability 2 months ago

Agreed on the "internal path disclosure", the title is now a bit misleading though

ahmedvienna has been awarded the disclosure bounty
The fix bounty is now up for grabs
The researcher's credibility has increased: +7
ahmedvienna
2 months ago

Researcher


Can you please assign it a CVE

Michael Kaufmann marked this as fixed in 2.0.10 with commit 7b08a7 2 months ago
The fix bounty has been dropped
This vulnerability has been assigned a CVE
This vulnerability is scheduled to go public on Jan 29th 2023
Michael Kaufmann published this vulnerability 2 months ago
ahmedvienna
2 months ago

Researcher


Hello. The CVE for this Vulnerability hast Not Bern published. When will you publish IT ?

Michael
2 months ago

Maintainer


It's literally a note above your comment, it is scheduled to go public on Jan 29th...why so impatient? Gotta give users time to update before this report shows exactly how to the exploit works

to join this conversation