@xhacking_z@instagram No, they have their own platform even at the time when I reported this (2023). They used HackerOne/Bugcrowd to make paying bounties easier
A vulnerability I discovered in @instagram in 2023 allowed an attacker to determine whether private account A follows private account B (and vice versa) directly, without having access to the followers/following lists of either account.
By 'blocked by default' I mean explicit authorization would be required between two origins to allow framing, similar to how SOP works where a CORS header is needed for cross-origin requests
If browsers were designed today from scratch, cross-origin framing would very likely be blocked by default, greatly reducing clickjacking vulnerabilities, and the only reason I see that it is still allowed by default in today's browsers is backward compatibility
@ZohairAtique@javarevisited No, in https the entire http request is encrypted, including the path and query parameters
ISP know the website you are visiting through:
- DNS queries
- SNI during the TLS handshake
- Destination IP address
According to this BBP logic, it is okay for someone to add a reaction on your behalf since document admins -might- notice that in version history (which is private logs for the document) lol.