Page 17 of 20

Posted: 2022-06-14 05:27
by Steven W
frfr.jpg
frfr.jpg (363.95 KiB) Viewed 8241 times

Posted: 2022-06-15 00:56
by Steven W
right.jpg
right.jpg (109.8 KiB) Viewed 8237 times

Posted: 2022-06-17 23:22
by !
20220617_232209.jpg
20220617_232209.jpg (20.89 KiB) Viewed 8226 times

Posted: 2022-06-18 05:16
by Steven W
! wrote:
2022-06-17 23:22
20220617_232209.jpg
:lol:

Eh, this isn't funny, but kinda amazing. Youtube, for whatever reason decided to auto-play this (I'm not embedding, will embed a shorter vidya):https://www.youtube.com/watch?v=3fT5K2SIXDQ

Anyway @ about 6:55 I saw this scene:



Absolutely fucking incredible.

Posted: 2022-06-18 05:43
by Steven W
I was greeted with yet another message in Outlook recently (not muh screenshot):
112535-m365-advert.png
112535-m365-advert.png (90.69 KiB) Viewed 8224 times
eat-at-joes-looney-tunes.gif
eat-at-joes-looney-tunes.gif (187.47 KiB) Viewed 8224 times

Posted: 2022-06-18 05:59
by Steven W
https://arstechnica.com/information-tec ... itics-say/
Microsoft's latest failing came to light on Tuesday in a post that showed Microsoft taking five months and three patches before successfully fixing a critical vulnerability in Azure. Orca Security first informed Microsoft in early January of the flaw, which resided in the Synapse Analytics component of the cloud service and also affected the Azure Data Factory. It gave anyone with an Azure account the ability to access the resources of other customers.

From there, Orca Security researcher Tzah Pahima said, an attacker could:
  • Gain authorization inside other customer accounts while acting as their Synapse workspace. We could have accessed even more resources inside a customer’s account depending on the configuration.
  • Leak credentials customers stored in their Synapse workspace.
  • Communicate with other customers’ integration runtimes. We could leverage this to run remote code (RCE) on any customer’s integration runtimes.
  • Take control of the Azure batch pool managing all of the shared integration runtimes. We could run code on every instance.
Third time’s the charm

Despite the urgency of the vulnerability, Microsoft responders were slow to grasp its severity, Pahima said. Microsoft botched the first two patches, and it wasn't until Tuesday that Microsoft issued an update that entirely fixed the flaw. A timeline Pahima provided shows just how much time and work it took his company to shepherd Microsoft through the remediation process.
Perhaps we can 30 percent off?

Posted: 2022-06-18 06:26
by Steven W

Posted: 2022-06-18 06:29
by Steven W
ie.jpg
ie.jpg (2.43 MiB) Viewed 8224 times

Posted: 2022-06-21 07:11
by Steven W
blockbuster.jpg
blockbuster.jpg (17.83 KiB) Viewed 8188 times

Posted: 2022-06-26 08:29
by Steven W
da_stamper.gif
da_stamper.gif (1.39 MiB) Viewed 8154 times