Light

Episode #862 Quiz

QWACs On? or QWACs Off?
Date: 2022-03-15 | Length: 1.75 hrs | Episode page at twit.tv

About this episode

Patch Tuesday fixed 71 Windows flaws, including remote code execution, privilege escalation, and Edge issues; Android and Firefox also received emergency patches for active zero-days. Binarly found 23 InsydeH2O UEFI flaws, risking Secure Boot bypass, persistence, and backdoors. Linux and QWAC certificate proposals likewise threaten trust, integrity, and browser security.

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

NameEmail

Question 1: In the Firefox zero-day discussion, what condition could a remote attacker exploit to trigger arbitrary code execution in the XSLT flaw?

Question 1

In the Firefox zero-day discussion, what condition could a remote attacker exploit to trigger arbitrary code execution in the XSLT flaw?

Forcing a stale IPC message to bypass WebGPU validation Corrupting the browser cache to overwrite stylesheet metadata Removing an XSLT parameter during processing Injecting a malformed WebGPU shader into the graphics pipeline

Question 2: Which statement best captures the security impact of the InsydeH2O UEFI flaws Binarly found?

Question 2

Which statement best captures the security impact of the InsydeH2O UEFI flaws Binarly found?

They were limited to a single vendor and could not affect other manufacturers They could invalidate Secure Boot and BootGuard and enable persistent malware They could only crash firmware utilities without affecting boot trust They affected only operating-system loaders and had no firmware persistence value

Question 3: What unusual detail made NVIDIA's leaked driver-signing certificates immediately useful for signing malware components?

Question 3

What unusual detail made NVIDIA's leaked driver-signing certificates immediately useful for signing malware components?

The certificates were self-signed and manually imported by victims The certificates were wildcard TLS certs reused for kernel drivers The certificates were expired but still accepted without timestamps The certificates were revoked but remained trusted by all browsers

Question 4: What was the first of the two main technical models described for the EU's proposed QWAC system?

Question 4

What was the first of the two main technical models described for the EU's proposed QWAC system?

A replacement for TLS that would remove certificate chains entirely A browser-displayed banner based on JavaScript validation A mandatory DNS record that browsers would query for identity A browser extension installed by each national authority

Question 5: According to the episode, why did the Linux 'Dirty Pipe' flaw become especially actionable for privilege escalation?

Question 5

According to the episode, why did the Linux 'Dirty Pipe' flaw become especially actionable for privilege escalation?

It allowed overwriting data in arbitrary read-only files It allowed Netfilter to write beyond bounds in the heap It allowed remote overwrite of signed kernel modules over SSH It allowed bypassing cgroup release_agent checks from inside a container

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.