"Arbitrary File Read via file:// Protocol in cURL"
Well, you see... 🤦♂️
"Arbitrary File Read via file:// Protocol in cURL"
Well, you see... 🤦♂️
cURL’s file:// protocol handler is enabled by default, allowing access to local files on the system. This behavior enables an attacker with the ability to run cURL commands to read arbitrary files on the host by specifying file paths or using directory traversal techniques. Steps to reproduce: 1. Build cURL with default configuration (e.g., ./configure --with-ssl and make). 2. Run...
@stfn
The exploit can be mitigated by cutting all eth, wifi and power cables
@bagder I don't think you understand the severity of this exploit.
First, it says Severity 9-10, so that automatically means it is the exploit of the century
Second, if an attacker can get access to the curl binary with root permissions, they can just read arbitrary files, compromising the entire system.
Just wait till someone builds the next WannaCry with this
@bagder @mage_of_dragons if the attacker does that they generally also can run cat
… *sigh*
It’s a fscking command line tool. If you expose them over the network, you’re responsible for securing things yourself.
This is literally curl working as intended.
@bagder Maybe there is a secret contest for "Who creates the most stupid report for curl and gets published?"...
I somehow feel the urge to participate...
Severity: Critical 9 ~ 10
@bagder
I think this is partially the result of a certain Bash bug years ago that got labelled a security hole and called "shellshock".
Yes, it was a bug in bash, but bash executes with the exact same privilege as the user or process invoking bash, so cannot result in privilege escalation. The security hole was never in bash, it was in the (usually PHP) code passing unvalidated input from the webserver to bash.
Those PHP devs got to blame bash for executing unvalidated input, rather that taking the blame for passing unvalidated input to bash, so now want to blame every tool that is capable of doing unintended things simply by passing unvalidated input.
Such as passing a file:// url to curl without validation.
@bagder They even just say it: a person using this program can read files they’re allowed to read.
“An attacker who can run cURL commands on the system can read any local file that the user running cURL has permission to access”
@bagder I asked AI to graphically demonstrate my reaction to the uh... bug...report.
The text on screen was not supplied by me - but oh man it fits.
I am seriously considering to switch to windows over this.
Is there no security on Linux at all????
@bagder O_o
Thats like a support ticket for "I've deleted the Internet" while they just moved the internet explorer icon into the trash bin.
Anakin: curl's accepting all redirects
Padme: All but to file://, right?
Anakin: ...
Right. Just tested it and it does not redirect (because of course)
you should use that as description in the man page
“FILE Read or write arbitrary local files.”
(Did they even notice they could write files?)
these type of reports are a DDOS-attack against free software projects, wasting dev's time on a grand scale