You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
HP iLO4 authentication bypass: curl -H "Connection: AAAAAAAAAAAAAAAAAAAAAAAAAAAAA" No, that's not a crash PoC. That's a full blown auth bypass. sscanf into fixed buffer overwrites a flag field that bypasses auth. Yes, really. https://airbus-seclab.github.io/ilo/SSTIC2018-Slides-EN-Backdooring_your_server_through_its_BMC_the_HPE_iLO4_case-perigaud-gazet-czarny.pdf …
Nobody audits anything. Everything is insecure. *sscanf*. *s-fucking-scanf*. In a web server. I'm just going to start giving each device a /30 and sticking reverse proxies in front of everything. Let me guess: next the switch will have an IGMP code exec bug or something. Sigh.
Yeah, I've done that before, I had an IP-KVM in my home lab that was EoL and it only supported SSL2.0, ended up sticking a pocket router in front of it, VPN to router, connect to KVM.
Just scanned the project sources on my disk for scanf+%s, found them "just" in tests and examples. Not optimal since such codes tends to be copy&pasted @bagder.
I fear those are items listed on place 17 and below on my personal TODO list and new things to work on tend to appear above it...
You just WAF'd :)
WAFs are bullshit. Vulnerable apps will always be vulnerable. The goal here isn't to snake-oil paper over trivial exploits in bypassable ways, the point is to have a solid authentication step behind which to shove all the vulnerable mess.
How often is sscanf implemented insecurely?
100% of the time. It's insecure by spec.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
