This is an interesting, albeit well-known attack vector. A similar attack was used to attack Avast [0]. The author notes that write access could be used to inj

This is an interesting, albeit well-known attack vector. A similar attack was used to attack Avast [0]. The author notes that write access could be used to inject dangerous objects (e.g. malicious pickles) into the database. This is arguably a much more serious bug because it does not require DNS rebinding (such a request can be performed cross-origin) nor can it be mitigated by refusing to read the response (as Chrome is proposing to do). In short: the database modification attack is potentially much more severe, but as of yet no precise attack chain has been identified. However, I think it's very likely that some server software uses e.g. pickles in the database. [0] https://bugs.chromium.org/p/project-zero/issues/detail?id=679&redir=1 https://bugs.chromium.org/p/project-zero/issues/detail?id=67...