• 1 Post
  • 52 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle


  • My employer had an EV cert for years on our primary domain. The C-suites, etc. thought it was important. Then one of our engineers who focuses on SEO demonstrated how the EV cert slowed down page loads enough that search engines like Google might take notice. Apparently EV certs trigger an additional lookup by the browser to confirm the extended validity.

    Once the powers-that-be understood that the EV cert wasn’t offering any additional usefulness, and might be impacting our SEO performance (however small) they had us get rid of it and use a good old OV cert instead.




  • Port 22 is the default SSH port and it receives a TON of malicious traffic any time it’s open to the whole internet. 20 years ago I saw a newly installed server with a weak root password get infected by an IP address in China less than an hour after being connected to the open internet.

    With all the bots out there these days it would probably take a lot less time if we ran the same experiment again.






  • Worked in a small Unix team under a broader IT department at a university. The manager of our team was awesome in part because his attitude was “I deal with all the university politics so you can focus on your work”. Anybody who has worked at a large university knows what the politics can be like.

    The VP of IT retired and the replacement was hired from an IT department at another university. The new VP’s overall policy was “We will do things this way because that’s how we did it at my old university”. Within about 6 weeks we had a round of “layoffs” that targeted our manager and one other manager that was also known to push back against the university politics. They were the only two people let go out of a department of roughly 100.

    Within about a year of that happening every last member of our tight knit Unix team left for greener pastures.




  • Our web servers are locked down in such a way that you can’t copy data off of them using standard protocols like scp, ftp, and even http, etc. Our firewall blocks all such outbound traffic.

    This hacker found a bug in a framework used on our web servers that let him execute commands remotely. When commands to copy data off the server failed using those more typical methods he switched to a more novel (and difficult) method of leveraging DNS instead. He discovered we weren’t locking DNS down the same way we were locking other protocols down and used that as a way to extract data from our server.


  • I never would have thought of it but I recently saw a novel use of DNS to exfiltrate data from a compromised server.

    My employer takes security very seriously. Our public facing web servers are very thoroughly locked down, or so we thought. We contract with companies like HackerOne to perform penetration testing etc. One of their white hat hackers managed a remote command attack, and copied data off of the server via a string of DNS queries.

    Suppose the hacker owned the domain example.com, and he had his own authoritative nameserver for it. He just ran a series of commands that took, for example, a password file, and ran DNS queries for line1.example.com, line2.example.com, line3.example.com and so on for each line in the file. As a result the log file on his DNS server collected each line of the password file as it responded to each query.