Why exploits prefer memory corruption

Thanks to @HalvarFlake and @chompie1337!

https://pacibsp.github.io/2024/why-exploits-prefer-memory-corruption.html

Zoho ManageEngine security advisories:

• Authenticated SQL Injection Vulnerability (CVE-2024-5527) fixed in ADAudit Plus build 8110 CVE-2024-5527 (vendor 8.3 high) authenticated SQL Injection in file auditing configuration
• Authenticated SQL Injection Vulnerability (CVE-2024-5487) fixed in ADAudit Plus build 8110 CVE-2024-5487 (vendor 8.3 high) authenticated SQL Injection in attack surface analyzer's export option
• Authenticated SQL Injection Vulnerability (CVE-2024-36518) fixed in ADAudit Plus build 8110 CVE-2024-36518 (vendor 8.3 high) authenticated SQL Injection in attack surface analyzer's dashboard

No mention of exploitation. Mitre and NVD only have publish dates from yesterday 12 August 2024, even though the Zoho advisories marked them fixed 14 June 2024. Zoho also doesn't indicate when the advisories were published. Happy #PatchTuesday

#Zoho #vulnerability #cve

‼️Big day! NIST publishes standards for next-generation cryptography (cipher, digital signature) understood as resistant to attacks with future quantum computers. Migration will not be a piece of cake, but there’s time. https://nvlpubs.nist.gov/nistpubs/fips/nist.fips.203.pdf https://nvlpubs.nist.gov/nistpubs/fips/nist.fips.204.pdf https://nvlpubs.nist.gov/nistpubs/fips/nist.fips.204.pdf

Seeking help from an IT security person - please share!

I run an open source, federated event sharing site, #Gathio (https://gath.io). A few days ago, it was victim to a ransomware attack that deleted the database. I need a few hours of someone's time (paid of course!) to sit with me and go through my security configuration ASAP.

Sometimes, running open source, free, community services _sucks_.

fun Linux fact:

There are at least two places in the Linux kernel where performance-sensitive code paths use a, uh, retrospective approach to memory safety, where you do the memory read first (and suppress the occasional kernel page fault) and worry about making sure it was memory-safe later.

One of the two is in the SLUB allocator's lockless allocation fastpath: https://elixir.bootlin.com/linux/v6.10.4/source/mm/slub.c#L544
It (1) first loads the pointer to the current top freelist element, then (2) reads the next freelist pointer out of that element, and (3) does a double-wide atomic compare-exchange to check if it raced and replace the freelist head. The read in step (2) can return garbage or fault if someone else concurrently modified the freelist (basically it can be UAF), but in that case step (3) that uses the result of the read is guaranteed to fail, so it's fine.

The other one is in the Virtual File System layer, used for printing pathnames (like for getcwd()):
https://elixir.bootlin.com/linux/v6.10.4/source/fs/d_path.c#L50
As the comment there explains:

 * The source of the prepend data can be an optimistic load
 * of a dentry name and length. And because we don't hold any
 * locks, the length and the pointer to the name may not be
 * in sync if a concurrent rename happens, and the kernel
 * copy might fault as a result.
 *
 * The end result will correct itself when we check the
 * rename sequence count, but we need to be able to handle
 * the fault gracefully.

So this one can race so that OOB memory is copied into the path buffer, but the kernel will afterwards notice that the "how many rename operations have happened" counter has gone up (or that the "we are currently in the middle of a rename" bit is set), discard the result, and try again.

Quick update on Akamai's roadmap for post-quantum cryptography from @rsalz and myself:

https://www.akamai.com/blog/security/taking-steps-to-prepare-for-quantum-advantage

#PQC

Resorts World (one of the hotels defcon contracted with to offer rooms to con attendees) decided to pull some clown shit and announce they’re doing daily room checks for “hacking” as some knee-jerk response to the MGM ransom attack last year. Someone leaked the checklist they gave to employees and it’s even dumber than you thought.

Wireless hacking doesn't have to be a mess of dongles and ad-hoc code anymore.

Yesterday @virtualabs from Quarkslab and @rcayre from EURECOM released WHAD, a set of open source tools, libraries and firmware to make wireless security research easier.

WHAD implements 6 protocols (BLE, ZigBee, RF4CE, Unifying, ESB, LoRaWAN) and supports 11 different hardware devices, including 4 embedding our custom firmwares to extend their capabilities.

It can be used to sniff various protocols (BLE, 802.15.4, ZigBee, RF4CE, Enhanced Shockburst, Logitech Unifying and even unknown ones via its PHY support), packet injection, MITM attacks, device emulation, device sharing over TCP, and a number of other features and capabilities.

See the code repository here https://github.com/whad-team/whad-client

if AI wants to be useful, it can read the build instructions of a github readme and tell me which seventeen packages the author forgot to mention I need to install first

Losing my mind at this. Google says that cellsite simulators are being used to send SMS spam.

https://security.googleblog.com/2024/08/keeping-your-android-device-safe-from.html

We had a lot of fun handing out our first-ever #Vanguard Awards. If you couldn't be there, we've updated our blog with all the winners. Check it out at https://www.zerodayinitiative.com/blog/2024/8/1/introducing-the-vanguard-awards