Hypothetically speaking, could an attacker run a targeted attack on a network that would inject information into a victim's cache of recent TLS connections? Specifically, the master-key and sessionID of your existing session you'd maintain with a specific website the victim would likely visit later.
When the victim goes to connect to the website over https, the full handshake will be forgone and the client will attempt to renegotiate a session using the injected (and known by the attacker) master key and sessionID. In turn, allowing the attacker to eavesdrop on all following encrypted communications.
Is this correct, or is my understanding of TLS implementation incorrect? Of course, injecting the information is a mountain to climb all it's own; but I'm still learning a lot about TLS and asked myself this question.