Support the people who make the stuff you like. There's a good chance that without that, the stuff you like won't get made.

@GossiTheDog @reverseics @cR0w But could *non-admin* users access the DB of *other* users? SQLite or not, this should not be possible (in general...). If it was possible back then (as it was suggested by you and articles based on your comments), then now would be the best time for all to see what the problem was to check if the same or similar problem is present in the implementation that is to be released.

@GossiTheDog @reverseics @cR0w Great you chime in! Any plans to release that x-user Recall exploit you talked about?

https://infosec.place/notice/AieinAN5CpyKNShdvE

The offensive industry loves making shit up: the new rumor making the rounds is that my girlfriend works at NSO. As a matter of fact, my girlfriend is currently unemployed and looking for work as an event manager in Europe, so let me know if you come across interesting openings. Her only experience in the security industry is coming with me to a few conferences over the past year to look for work and learn more about this niche.

@cR0w @reverseics My theory is that a) URL's are the new filesystems and b) abstracting away control ("..") from data ("etc") would have an unacceptable overhead compared to SQL (ORMs) or even HTML (DOM sanitizers), so the memes are here to stay :)

Here is another #NameThatWare

Can you deduct or guess which device this is?
As always, hide your answer behind a CW to not spoil others.

#directoryTraversalMemes seem to become a classic, but I wonder if anyone has a list of specific payloads that trigger the different vulnerabilities of recent memory?

/cc @reverseics @cR0w

I published my analysis of the Series 9000 Brainalyzer exploit by Rick Sanchez:

https://video.infosec.exchange/w/jtR1V9N5ghHES5oayeBrrd

Did I miss anything?

#NoCVE

Why the Soviet Computer Failed

https://www.youtube.com/watch?v=dnHdqPBrtH8

Again, it's all about incentives...

KASAN is now available for your own Windows Drivers: https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/kasan

OK, but maybe Italy was an isolated case and ransom payment bans work elsewhere, right?

In fact, several countries ban the payment of ransom to kidnappers: Venezuela, Colombia, Nigeria...

Hey, let's take a look at Nigeria. Compared to it, the Italian mafia is peanuts. In Nigeria, kidnapping for ransom is an idustry. 7,568 abducted, 1056 killed in just one year.

In 2022, Nigeria passed a law, making ransom payments illegal. What effect did that have?

About what you'd expect by now:

Oh God, yes! When starting a qemu instance, you can pass it an fd on the command line for its listening socket for that chardev.

You can also tell it to listen on a TCP or UNIX socket, but as the starting process, you now need to try and connect multiple times until qemu is finally started and opened its listening socket. It also might never connect in case qemu fails to start. This is really annoying to handle properly in your code.

With the fd-passing, the parent process can create the listening socket, clear CLOEXEC on the socket, pass it to qemu and then connect to it. At that time it will either be open already or if qemu fails to start, the listening socket will be gone and the connect() fails.

I haven't tried it yet, but I need it for work and it sounds like a proper solution to a really annoying problem.

https://patchwork.kernel.org/project/qemu-devel/patch/20180205152455.12088-10-berrange@redhat.com/

@Proteas Note that in case of dogs numbers can be much higher.

@Proteas A toddler with an ice cream weighs about 10kg and moves about 0.5 m/s without dropping the ice cream.

Unattended children get an IBM System/370 and a Cobol starter lecture.

Another amazing video by 3Blue1Brown, prepare to get your mind blown:

https://www.youtube.com/watch?v=piJkuavhV50

#Math

Windows DWM Core Library Elevation of Privilege Vulnerability (CVE-2024-30051) https://www.coresecurity.com/core-labs/articles/windows-dwm-core-library-elevation-privilege-vulnerability-cve-2024-30051