Light

Episode #884 Quiz

TLS PRIVATE KEY LEAKAGE
Date: 2022-08-16 | Length: 1.75 hrs | Episode page at twit.tv

About this episode

Researchers passively and actively monitored billions of TLS handshakes, exploiting transient RSA signature faults in TLS 1.0–1.2. Faulty CRT-based PKCS#1 v1.5 signatures leaked private keys, enabling retrospective decryption and impersonation. Mitigations include validating signatures before sending, using RSA-PSS, and migrating to TLS 1.3’s encrypted, forward-secure handshake.

Your name and email are stored only in your browser local storage for convenience. They are not retained server-side.

NameEmail

Question 1: According to the episode, what specific flaw did Microsoft previously dismiss in its MSDT handling before it became CVE-2022-34713?

Question 1

According to the episode, what specific flaw did Microsoft previously dismiss in its MSDT handling before it became CVE-2022-34713?

A path traversal issue in .diagcab files that could place code in the Startup folder A buffer overflow in Outlook that crashed the mail client on message preview A privilege escalation in SMB compression on Windows 11 servers An NFS remote code execution flaw triggered by malformed file system calls

Question 2: What was the key operational difference between the passive TLS attack and the active TLS scans described in the episode?

Question 2

What was the key operational difference between the passive TLS attack and the active TLS scans described in the episode?

Passive observation targeted only TLS 1.3 sites, while active scans were limited to legacy SSLv3 endpoints Passive observation relied on captured handshakes, while active scans initiated many TLS connections to provoke faulty signatures Passive observation depended on decrypted traffic logs, while active scans depended on leaked certificate chains Passive observation required server-side access, while active scans required only DNS lookups and no TLS traffic

Question 3: Why does the episode say TLS 1.3 reduces the risk of this RSA fault attack compared with TLS 1.2?

Question 3

Why does the episode say TLS 1.3 reduces the risk of this RSA fault attack compared with TLS 1.2?

It eliminates all certificate signatures and replaces them with symmetric authentication It encrypts server certificates only after the client finishes authentication It forces all handshakes to use elliptic-curve keys and disallows RSA entirely It moves key exchange earlier and uses RSA-PSS signature padding

Question 4: What did the researchers report about the scale of their passive TLS collection before finding compromised keys?

Question 4

What did the researchers report about the scale of their passive TLS collection before finding compromised keys?

They collected 5.8 billion TLS handshakes and found nearly 2,000 non-validating signatures They collected 3.3 billion TLS handshakes and found several thousand compromised wildcard certificates They collected 580 million TLS handshakes and found nearly 200 non-validating signatures They collected 2.7 billion TLS handshakes and found about 127 non-validating signatures

Question 5: What specific practical warning did the episode give about publicly exposing services like SMB and VNC?

Question 5

What specific practical warning did the episode give about publicly exposing services like SMB and VNC?

Only RDP and web mail should be exposed, while SSH and VPN should be avoided because they are less secure Only Windows services should be hidden, while non-Windows remote services are generally safe to expose Only services that must be anonymously public should be exposed, and others should stay behind VPN or SSH Only services with strong passwords should be exposed, and anonymous access is acceptable if logging is enabled

Cancel

My Data//Security & Privacy//Clear Local Data

© 2026 Ken ArmstrongSecurity Now™ is a trademark of TWiT LLC. All trademarks and copyrights of the Security Now podcast are respected and reserved to their respective holders.
This is a hobby project made with love and admiration for what Steve Gibson and Leo Laporte have built over 20 years.