News for hackers. Stuff that matters.
Re:Show HN: Anycomplete by __s on Tuesday November 29, 2016 @06:07PM (#13066980)
But they aren't piping to sh..
Re:Show HN: Anycomplete by kirushik on Wednesday November 30, 2016 @09:17AM (#13070857)
The infamous Barmin's patch doesn't have any `sh` mentions either:

``` echo "test... test... test..." | perl -e '$??s:;s:s;;$?::s;;=]=>%-{<-|}<&|`{;;y; -/:-@[-`{-};`-{/" -;;s;;$_;see' ```

Re:Show HN: Anycomplete by cyphar on Tuesday November 29, 2016 @06:27PM (#13067124)
Yeah, but if there's a code execution vulnerability in any of the tools in the pipeline it's as good as piping to sh.
Re:Show HN: Anycomplete by duaneb on Tuesday November 29, 2016 @09:03PM (#13067838)
Yup! Using curl at all is downright dangerous.

/s

Re:Show HN: Anycomplete by cyphar on Tuesday November 29, 2016 @09:25PM (#13067952)
Well, it's all about risk assessment. Curl has had RCE security bugs before[1]. That doesn't mean curl is "downright dangerous" it just means that "it's safe because it doesn't pipe to sh" is also not a correct thing to say.

[1]: http://blog.volema.com/curl-rce.html

Re:Show HN: Anycomplete by verandaguy on Wednesday November 30, 2016 @10:29AM (#13071464)
Incidentally, cURL just had a major security audit. The dev is doing due diligence to avoid RCE vulnerabilities.
Re:Show HN: Anycomplete by duaneb on Wednesday November 30, 2016 @10:14AM (#13071352)
Piping to jq and sed is just fine. I'm not sure where sh comes into this...
Re:Show HN: Anycomplete by cyphar on Wednesday November 30, 2016 @11:33PM (#13077194)
Unless there's a bug in curl, jq or sed that leads to an RCE, which is what my point was.
Re:Show HN: Anycomplete by TeMPOraL on Wednesday November 30, 2016 @02:48AM (#13069145)
I suppose 'devoply pattern-matched "curl -sS <sth> | <sth else>" to "don't do that". I think that because that's exactly what I did now; it took me a few seconds to realize that - this time - the invocation is mostly harmless.