Patching?

In this economy?

SEC Consult SA-20241030-0 :: Query Filter Injection in Ping Identity PingIDM (formerly known as ForgeRock Identity Management) (CVE-2024-23600)

https://seclists.org/fulldisclosure/2024/Oct/18

@pid_eins but do we have the software/hardware infrastructure needed to actually make this secure on a typical Linux desktop machine?
To me, the core purpose of disk encryption is protect a machine against an attacker who steals the entire, powered-off machine; and it's easy to mess up unattended disk encryption so that this is easy to break. The communication with the TPM needs to be protected against interposer attacks somehow (see https://www.nccgroup.com/us/research-blog/tpm-genie-interposer-attacks-against-the-trusted-platform-module-serial-bus/ ); the disk ideally should not just be encrypted but also integrity-protected (because in some settings, the disk encryption is then relied on for security against adaptive online attacks instead of security against a one-time-snapshot passive attacker); you need rollback protection against someone booting a super vulnerable outdated OS image; bugs in device drivers turn into disk encryption bypasses (and notably Linux basically trusts PCI devices to not be actively evil); and so on.

So I'm worried that providing TPM-based disk unlock as an easy-to-configure mechanism might give people a false sense of security. With password-based disk encryption, to me, the core security promise is easy: If someone steals your (not-too-recently-) powered-off computer, they can't get any of the data out of it unless they break your password. With TPM-based unlock, the story is a lot more complex...

tmp.0ut Volume 4 is happening! Our call for papers is now open, and we're excited to see what you've been working on 👀 read the full announcement here: https://tmpout.sh/blog/vol4-cfp.html

@buherator Oh my god I had no idea (or maybe i blanked it out?!) that talk had been video'd and made it to youtube.

My main memory of that talk is that i was the closing talk of the con, and at some point mid way thru i realised i was out of time, and instead of doing the usual thing of rushing it thru to the end which no one enjoys or remembers, I decided that anyone who needed to leave to go pick up their kids or whatever could just get up and leave, and i would keep going until I was done. Despite poor conference organiser @sputina sitting in the front row having a conniption fit making "wrap it uppppp" gestures, and then eventually also just giving up and crying to herself. I don't recall seeing anyone leave, but maybe that's just my head-canon version of it.

This was a pretty cathartic (albeit maybe a bit self indulgent) talk to write and do.

I ... was not expecting it to have held up so well, and, having worked with @dave_aitel and also read a lot of his output over the years, I respect dave a heap, so getting a 10 outta 10 from dave is ... I'm actually kinda chuffed about that.

OK! Want to self-host your own bots now #BotsInSpace is going away?

I've made the *simplest* possible server just for you!

https://gitlab.com/edent/activity-bot/

Upload two files to your server (index.php and .htaccess), fill in a couple of details, and… that's it!

This is designed for write-only bots. It isn't interactive, it won't store or reply to messages sent to it, but it will post hashtags, links, mentions, and images.

You can see the sample bot @bot

Feedback very welcome!

It was weird that I couldn't find in this Sophos report *what* was actually exploited aside of CVEs and codenames... then CVE info showed they were Sophos devices :P

https://news.sophos.com/en-us/2024/10/31/pacific-rim-timeline/

Recently, I tried running TinyInst against a target written in Objective C and... the performance was ... not great. Let's analyze why that was and how to fix it:

Firstly, technical background: TinyInst marks the code sections of instrumented modules non-executable. Then (being a debugger), it catches exceptions raised while attempting to execute the original code and redirects execution to the rewritten code instead.

Exception handling is not very fast, but it only happens when non-instrumented code calls into an instrumented module. All callls from instrumented into instrumented code get optimized. This is why TinyInst works best when instrumented modules are selected so that they form a whole and calls into their group happen rarely. A handful is fine, but you'll notice if there are thousands.

How does Objective C mess this up? Because method calls in Objective C happen through objc_msgsend, which is a part of libobjc module. So even if you have calls from module abc to the same module, What you end up with is abc->libobjc->abc.

If libobjc is not instrumented, then libobjc->abc transitions will cause slowdowns. On the other hand, if you do instrument libobjc, then any Objective C calls from any non-instrumented module will cause slowdowns. So, no good solution, right?

But what if we instrument libobjc ins such a way that it only runs instrumented if it's called from other instrumented code? This is surprisingly simple to implement, we just skip marking its code non-executable during instrumentation, but it will still runs instrumented code when called from other instrumented code due to optimization mentioned earlier.

The effect: an order of magnitude better performance and we get libobjc instrumented "for free" (it doesn't cause any additional entries)

This is now implemented in TinyInst in the form of -instrument_transitive, which will instrument a module only for calls from other instrumented modules.

tl;dr if you run Objective C code under TinyInst and are experiencing slowdownsm, try -instrument_transitive libobjc.A.dylib. But it will no doubt improve performance in other scenarios as well.

QNAP NAS Zero-Day Vulnerabilities (CERT-EU Security Advisory 2024-115)

On October 29 and 30, 2024, QNAP released patches for two critical zero-day vulnerabilities, CVE-2024-50387 and CVE-2024-50388, affecting NAS devices. These vulnerabilities allow remote attackers to gain root access and execute arbitrary commands on compromised devices.

https://www.cert.europa.eu/publications/security-advisories/2024-115/

[Dailydave] Old Infosec Talks: Metlstorm's Take on Hacky Hacking

https://seclists.org/dailydave/2024/q4/1

🧙‍♀️

[RSS] Using AFL++ on bug bounty programs: an example with Gnome libsoup (2024.10.30)

https://offsec.almond.consulting/using-aflplusplus-on-bug-bounty-programs-an-example-with-gnome-libsoup.html

[RSS] Give Me the Green Light Part 2: Dirty Little Secrets

https://www.redthreatsec.com/blog/give-me-the-green-light-part2-dirty-little-secrets

[RSS] Paranoids' Vulnerability Research: NetIQ iManager Security Alerts | Paranoids | Yahoo Inc.

https://www.yahooinc.com/paranoids/paranoids-vulnerability-research-netiq-imanager-security-alerts

[RSS] Exploiting a Blind Format String Vulnerability in Modern Binaries: A Case Study from Pwn2Own Ireland 2024

https://www.synacktiv.com/en/publications/exploiting-a-blind-format-string-vulnerability-in-modern-binaries-a-case-study-from

e-voting fail including a "hidden" tab in an Excel file.
My bingo card for this year is getting full.

The Colorado Secretary of State’s Office inadvertently posted a spreadsheet to its website with a hidden tab that included voting system passwords.
https://apnews.com/article/colorado-election-voting-system-passwords-0a71d0c1fe85fc9712d895280fd519a2

Smashing the limits: Installing Windows XP in DOSBox-X

A couple of months ago, I tried to install (the unsupported) Windows XP in DOSBox-X. Well, it was not easy.

https://fabulous.systems/posts/2023/07/installing-windows-xp-in-dosbox-x/

#retrocomputing

Special Authority Data Mart created to allow me to see which profiles have special authorities, and to capture the information over time into a file.
💙 #IBMi #rpgpgm #IBMChampion
https://www.rpgpgm.com/2024/10/special-authority-data-mart.html

Put up the slides for my Bluehat 2024 presentation on improvements to OleView.NET https://github.com/tyranid/infosec-presentations/blob/master/Bluehat/2024/DCOM%20Research%20for%20Everyone!.pdf You can also grab v1.15 of OleView.NET from the PS Gallery which has the new features to generate proxy clients on the fly.