$ openssl x509 -in cert -inform DER -out burp_suite.crt We need to instead convert it to ".crt" and move it into the "/usr/local/share/ca-certificates" directory as shown below. The file we just downloaded is in the DER format. On Ubuntu it's actually pretty simple (and presumably simple on other Debian distros like Kali). This is a simple fix with a web browser, but what about with an OS? The browser sees that the proxy uses PortSwigger's CA and then drops the connection. Many folks who have used Burp Suite to intercept traffic from a browser will be familiar with this problem. How do we get around this? Step 2: Import the Burp Suite Cert in Ubuntu In this instance, Curl is behaving appropriately and many tools will give you this same response. Tools should validate the TLS/SSL cert and drop the connection if they aren't correct (if the tool you're looking at doesn’t do this, that's a finding). For example, here I am curling my website.įantastic, it looks like that gives us a 301 response (redirecting us to the https version of the site), what happens when we follow it?Īh, that's right. We can actually start intercepting traffic. Here, 192.168.122.1 on port 8080 is where I have my Burp proxy listening (I use KVM and this is the default subnet VM's spawn on in case you are confused). The following commands will do this: $ export http_proxy="" This can be done very easily in many shells such as Bash and Zsh. For reference, all of this testing was performed on an Ubuntu 19.10 VM.įirst things first, we need to set up our proxy. The following is a simple means of intercepting the traffic of Linux CLI tools with Burp Suite. Obviously being able to intercept and inspect that traffic is very helpful for security researchers, Pentesters, Red Teamers, bug bounty hunters, or whatever you call yourself. Many of these tools interact with APIs on remote systems. Recently I've been looking into flaws in a handful of Linux CLI tools. Intercept Linux CLI Tool Traffic January 11, 2020
0 Comments
Leave a Reply. |