The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,860 other subscribers
«
»

Detecting the use of “curl | bash” server side | Application Security

Posted by jpluimers on 2016/04/20

From the “let people know when they are stupid” department:

Another reason not to pipe from curl to bash. Detecting curl | bash serverside.

Source: Detecting the use of “curl | bash” server side | Application Security

–jeroen

This entry was posted on 2016/04/20 at 12:00 and is filed under Development, Python, Scripting, Software Development. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “Detecting the use of “curl | bash” server side | Application Security”

  1. Copy-Paste from Website to Terminal – always paste via an intermediate text editor « The Wiert Corner – irregular stream of stuff said

    2016/11/22 at 12:01

    […] copy/pasting to the console is just as risky as piping curl through bash or another shell. You can actually detect that server-side (and abuse […]

    Reply

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

«
»