Light

Episode #852 Quiz

December 33rd
Date: 2022-01-04 | Length: 1.5 hrs | Episode page at twit.tv

About this episode

Episode 852 covered Log4j’s fifth patch, 2.17.1, fixing another arbitrary code execution flaw via remote configuration loading and deep Java dependencies, plus Microsoft Defender Log4j scanner false positives and Alibaba’s disclosure dispute. It also explained Exchange’s 32-bit signed version overflow, forcing a PowerShell workaround that resets updates to December 33rd.

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

NameEmail

Question 1: What specific condition made the fifth Log4j flaw harder to exploit than the original Log4Shell vulnerability, according to the episode?

Question 1

What specific condition made the fifth Log4j flaw harder to exploit than the original Log4Shell vulnerability, according to the episode?

It required a privileged local login on the vulnerable host It required direct access to the Java heap It required attacker control over the configuration It required a successful DNS cache poisoning attack

Question 2: What did Microsoft Defender for Endpoint incorrectly alert on in connection with its Log4j scanner rollout?

Question 2

What did Microsoft Defender for Endpoint incorrectly alert on in connection with its Log4j scanner rollout?

Network devices identified as Cobalt Strike implants Sensor tampering in memory detected by OpenHandleCollector.exe Chrome updates identified as PHP backdoors Office documents identified as Emotet payloads

Question 3: Why did Alibaba Cloud face a six-month suspension from China’s MIIT, according to the episode?

Question 3

Why did Alibaba Cloud face a six-month suspension from China’s MIIT, according to the episode?

It failed to promptly inform the government about the Log4j vulnerability It delayed patching Apache Log4j on its internal Java services It refused to cooperate with China’s cybersecurity reporting databases It shared Apache’s patch details before Apache released them

Question 4: What update did Microsoft use to work around the Exchange Server Y2K22 bug?

Question 4

What update did Microsoft use to work around the Exchange Server Y2K22 bug?

A registry patch that changed Exchange to unsigned version numbers A cumulative update that advanced the version format to 2022 01 01 0001 A PowerShell script that reset the scan engine version to 21 12 33 0001 A transport queue repair utility that reindexed stuck messages

Question 5: What unusual browser architecture did DuckDuckGo say it would use for its desktop browser?

Question 5

What unusual browser architecture did DuckDuckGo say it would use for its desktop browser?

A fork of Chromium with privacy features removed A WebKit port bundled with a proprietary networking stack A Gecko fork wrapped in a hardened privacy shell A custom engine built on the OS-provided rendering engines

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.