How we got LFI in apache Drill (Recon like a boss)

Hi Everyone,

As promised in last blog, today I am gonna write this blog about few things on LFI. special thanks to one and only Jobert.

Few months back i got private invite in hackerone platform. As you know Recon plays a major role while hacking on a program. Recon doesn’t always mean to find subdomains belonging to a company, it also could relate to finding out how a company is setting up its properties and what resources they are using.

What is LFI?

Local File inclusion (LFI), or simply File Inclusion, refers to an inclusion attack through which an attacker can trick the web application in including files on the web server by exploiting functionality that dynamically includes local files or scripts. The consequence of a successful LFI attack includes Directory Traversal and Information Disclosure as well as Remote Code Execution.
Typically, Local File Inclusion (LFI) occurs, when an application gets the path to the file that has to be included as an input without treating it as untrusted input. This would allow a local file to be supplied to the include statement.

After looking into shodan and for that domain I found one , and Istarted digging there and no success for intial hours.Later i found tabs like Query , storage tab , so i quickly gone to their document to read all things and how it works at .

Few things on query :

The query specifies the data source location and includes data casting.Specifying the Data Source Location ¶The optional USE statement runs subsequent queries against a particular storage plugin. The USE statement typically saves typing some of the storage plugin information in the FROM statement. If you omit the USE statement, specify a storage plugin, such as dfs, and optionally a workspace, such as default, and a path to the data source using dot notation and back ticks. 
For example:

After understating few document , Itook help from the great hacker Jobert Abma (Co-founder of HackerOne), he told we can try to get LFI.

Wait for a moment and listen music.

after few minutes jobert come up with below json file , which he wrote as dfs storage method :

{   "type": "file",  
"enabled": true,
"connection": "file:///",
"config": null,
"workspaces": { "etc":
{ "location": "/etc",
"writable": false,
"defaultInputFormat": "tsv" }
}, "formats": {
"tsv": {
"type": "text",
"extensions": [ "tsv"],
"delimiter": "\t"

and just call that from query tab


select * from dfs.etc.`passwd`

and wow! all we got is:

So , It’s time to partyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy!

We then tried for multiple json file as dfs storage method and we got success.

woot woot!

I always believed that sharing is caring, and I have been learning from multiple security researchers. Hope You liked this finding. Many more are coming. Stay tuned. DM is open for any questions on twitter (Gujjuboy10x00 ,