Really interesting post, thanks. It's kind of ridiculous how much data gets sent back and forth for some of these types of things, and how the developers don't really seem to put a lot of concern...
Really interesting post, thanks. It's kind of ridiculous how much data gets sent back and forth for some of these types of things, and how the developers don't really seem to put a lot of concern into whether that data should be public. I feel like the recent trend towards SPAs has added a lot of laziness around this, where a giant JSON file sent to the client is just treated as data that's the same as what would be in a site's database, without consideration that someone can examine the file outside the context of the app itself.
As a security researcher I've loved the recent trend of hiding everything behind a REST API. So many companies have extremely weak rate limiting in place, as well. Take a look at this tool -...
As a security researcher I've loved the recent trend of hiding everything behind a REST API. So many companies have extremely weak rate limiting in place, as well.
I can go from a network request in Chrome -> Right click, copy as Curl -> to straight python code in less than 5 seconds. From here you can play around with whatever you want, or iterate over large amounts of data really quickly.
It's trivialized web scraping - you no longer need to write complicated CSS queries or parse HTML on a lot of modern websites; it's in an easy to use, JSON format already!
That's definitely interesting. So many routes for industrial espionage that no one is protecting.
Really interesting post, thanks. It's kind of ridiculous how much data gets sent back and forth for some of these types of things, and how the developers don't really seem to put a lot of concern into whether that data should be public. I feel like the recent trend towards SPAs has added a lot of laziness around this, where a giant JSON file sent to the client is just treated as data that's the same as what would be in a site's database, without consideration that someone can examine the file outside the context of the app itself.
I think it's not quite the same as what you were looking at in this post, but this was a recent interesting example of a data leak on Tesla's site as well: https://twitter.com/JakeLangford6/status/1097688632809455616
As a security researcher I've loved the recent trend of hiding everything behind a REST API. So many companies have extremely weak rate limiting in place, as well.
Take a look at this tool - curl.trillworks.com.
I can go from a network request in Chrome -> Right click, copy as Curl -> to straight python code in less than 5 seconds. From here you can play around with whatever you want, or iterate over large amounts of data really quickly.
It's trivialized web scraping - you no longer need to write complicated CSS queries or parse HTML on a lot of modern websites; it's in an easy to use, JSON format already!