Newsletter Archives

• Dealing with printers

  Posted on March 22nd, 2021 at 01:00 Susan Bradley Comment on the AskWoody Lounge

  PATCH WATCH

  

  By Susan Bradley

  Keeping printers up to date

  Once upon a time, I purchased an HP LaserJet 4L printer that would just keep on printing, year after year, until the plastic door on the top of the printer finally broke off. After my initial installation, the printer driver was never updated.

  Read the full story in the AskWoody Plus Newsletter 18.11.0 (2021-03-22).

  AskWoody Plus Newsletter, Patch Watch AskWoody Plus Newsletter, Blue screens of death, Exchange Server, Patch Lady Posts, printers

• MS-DEFCON 2 — It’s time to defer March updates

  Posted on March 8th, 2021 at 14:45 Susan Bradley Comment on the AskWoody Lounge

  ISSUE 18.9.1 • 2021-03-08

  

  

  By Susan Bradley

  It’s the start of the patching week.

  We are a day away from the official start of patching season. While Microsoft started the March patching madness early, with a critical patch needed for its mail servers, we have yet to see what’s in store for those of us that merely use their Windows as workstations.

  Read the full story in the AskWoody Plus Alert 18.9.1 (2021-03-08).
  Learn more about MS-DEFCON!

  AskWoody Plus Newsletter, Windows Patches/Security AskWoody Plus Newsletter, Exchange Server, MS-DEFCON 2

• Exchange Server elevation of privilege bug acknowledged

  Posted on February 6th, 2019 at 12:04 woody Comment on the AskWoody Lounge

  Remember the 0day exploit in Microsoft Exchange that we talked about two weeks ago?

  As I suspected, your Exchange Server is only vulnerable to a man-in-the-middle attack. It isn’t an all-purpose attack: The miscreant has to be able to sit in the middle of an interaction with the Server.

  Microsoft finally has an explanation in ADV190007 | Guidance for “PrivExchange” Elevation of Privilege Vulnerability.

  A planned update is in development. If you determine that your system is at high risk then you should evaluate the proposed workaround.

  The workaround is a one-line PowerShell script that @b talked about last week.

  Windows Patches/Security 0day, Exchange Server, PrivExchange