Openness to responsibly disclosed external vulnerability research is crucial for modern software maintainers and security teams. Changes in upstream dependency code may have pulled the safety rug out from underneath widely trusted core libraries, leaving millions of services vulnerable to unsophisticated attacks. The impact of even a single reasonably well-distributed supply-chain security vulnerability will be felt by engineering teams across many applications, companies, and industries.
We’d like to discuss an IP address parsing vulnerability first discovered in private-ip, a small and infrequently maintained yet critically important NodeJS package for determining if an IP address should be considered part of a private range or not. We’ll talk about not only the implications of this CVE but taking the main idea and applying it across multiple programming languages in uniquely disturbing ways.
Sometimes, the effects of code rot are even more far-reaching than we could possibly expect, and if you pull on a thread, it just keeps going. Sometimes, you get lucky when you know exactly what you’re looking for. Sometimes, it’s hard to convince other technically-minded folks that a seemingly trivial implementation flaw is dangerous in capable hands.
This talk is beginner as well as advanced-friendly; we’ll show you the basics a hacker or a programmer needs to know about IP address parsing and how to tell your octal from your decimal along the way.
Researchers involved in this work:
– Victor Viale: https://github.com/koroeskohr, koroeskohr
– Sick Codes: https://github.com/sickcodes, sickcodes
– Kelly Kaoudis: https://github.com/kaoudis, kaoudis
– John Jackson: https://www.johnjhacking
– Nick Sahler: https://github.com/nicksahler, tensor_bodega
– Cheng Xu: https://github.com/xu-cheng
Selected press coverage (as of May ’21)
Currently released advisories related to this work (as of May ’21)