This must be the ultimate #C64

Dual SID chips, tube amp, full mechanical keyboard.

Cisco security advisories includes a zero-day:

• Cisco Meraki Systems Manager Agent for Windows Privilege Escalation Vulnerability
  CVE-2024-20430 (7.3 medium) incorrect handling of directory search paths (CWE-427: Uncontrolled Search Path Element) to EoP
• Cisco Smart Licensing Utility Vulnerabilities
  • CVE-2024-20439 (9.8 critical) Cisco Smart Licensing Utility Static Credential Vulnerability
  • CVE-2024-20440 (9.8 critical) Cisco Smart Licensing Utility Information Disclosure Vulnerability
• Cisco Identity Services Engine Command Injection Vulnerability
  CVE-2024-20469 (6.0 medium) insufficient validation of user-supplied input to authenticated command injection (the attacker must have valid Administrator privileges)
  • The Cisco PSIRT is aware that proof-of-concept exploit code is available for the vulnerability that is described in this advisory.
• Cisco Expressway Edge Improper Authorization Vulnerability
  CVE-2024-20497 (4.3 medium) inadequate authorization checks for Mobile and Remote Access (MRA) users could allow an attacker to intercept calls or make phone calls spoofing another phone number
• Cisco Duo Epic for Hyperdrive Information Disclosure Vulnerability
  CVE-2024-20503 (5.5 medium) improper storage of an unencrypted registry key could allow an authenticated, local attacker to view sensitive information in cleartext

EDIT: What @BleepingComputer took away out of this is that CVE-2024-20439 is a backdoor admin account: Cisco warns of backdoor admin account in Smart Licensing Utility

#zeroday #cisco #patchtuesday #vulnerability #CVE_2024_20469 #cve #CVE_2024_20439

(indistinctly yelling at the computer)

this is a series expansion of a natural logarithm

‘Everything happens for a reason’ sounds less comforting when the reason is very fucking poor planning

We want your old GPUs that were destined to become e-waste.
We're repurposing outdated GPUs to tackle challenging computer security and program analysis problems. https://buff.ly/3XsbdgJ

In light of the Internet Archive losing its appeal to hachette, I just wanted to point out some websites you should avoid:

* https://annas-archive.li/
* https://downmagaz.net/
* https://ebook-hunter.org/
* https://forcoder.net/
* https://freemagazines.top/
* https://liber3.eth.limo/

If you were to download books from these websites, you might cut into hachette's more than three billion dollars of annual revenue. So make sure to avoid those websites and the following:

* https://libgen.is/
* https://oceanofpdf.com/
* https://pdfroom.com/
* https://pdfstop.com/
* https://pdfdrive.to/
* https://pdfmagazines.club/
* https://sci-hub.se/
* https://singlelogin.re/
* ... or any of the other sites listed at https://rentry.co/megathread-books

#internetarchive

Fucking @buherator trying to kill me with this home made Palinka

@bagder To put in perspective:
- JPEG: libjpeg 6b encoder+decoder: 24,200 lines of C
- JPEG: libjpeg-turbo encoder+decoder: 127,000 of C and ASM (multi architectures)
- JPEG2000: openjpeg encoder+decoder: 50,000 lines of .C
- JPEG2000: Kakadu commercial encoder+decoder: 214,000 lines of C++ (only coresys component)
- libjxl: 150,000 lines for the core library, encoder+decoder (deps excluded)
(All above includes blank lines + inline doc)
So this is pretty much standard for a modern codec

⚡ Operator Fabric is an open source platform built by the LF Energy Foundation (https://lfenergy.org/) for use in electricity, water and other utility operations.

Last May we did a security audit sponsored by the Open Source Technology Improvement Fund (https://ostif.org) 🙏

Read a summary of our findings and find the full report here:

https://blog.quarkslab.com/audit-of-operator-fabric.html

Ongoing slab hardening efforts

Recently, there have been multiple efforts to make the exploitation of slab memory corruptions harder.

🧵[1/5]

I started a couple of forest fires to heat my burrito and I'm surprised by the results! It was still frozen in the middle by the end of the experiment, so it's far from perfect, but I think forest fires have a lot of potential and will revolutionize the burrito heating industry!

@whitequark incidentally, there is a beautiful parallel which I always make when discussing security and "1st papers about an attack": the so-called "nth country problem".

This is an issue in nuclear proliferation which, in a few words, says that the nth country to become a nuclear power has the benefit of knowing that it works, and what works (unlike the Manhattan Project which started on the basis of pure theory).

The "nth country problem" was actually tested by the USA by giving three Physics PhD students access to all open literature on nuclear weapons and asking them to design a weapon. They did and analysis by LANL weapons designers actually showed that it would go b00m.

Hence, even if the 1st paper is extremely unlikely (compare to the Trinity test of the Pu implosion device - there was quite a bit of uncertainty that it would work) it does not mean that it cannot be done.

@whitequark undeniably true. I'd also add that these attacks, while pretty niche, do attract the attention to a platform which was previously deemed "unbreakable".

In many ways this is similar to how work by people in the 90s (TESO, for example) drew my attention to µcode and John Heasman's work on ACPI to NIC firmware. Now look at the µcode panorama where you have an attack a day or firmware where there's an attack an hour (OK, sort of)

Nothing like breaking a myth.

I’ll reiterate what many others have said about the yubikey story - unless you’re the target of super sophisticated actors who do not want you to know they’ve stolen your yubikey*, this is a bit of a non-event and highlights the importance of keeping track of your yubikeys. Please don’t toss them, but do keep an eye out for further developments. Once an issue like this is identified, it attracts a lot of attention from many smart people and there may will be other findings in the future, but for now, yubikeys are good enough for most of us.

* I know there are a bunch of people convinced you’re being pursued by these advanced adversaries. I worry about you. For many reasons.

Tired of using debuggers and manually exploring the program's state space? Too annoying to find the inputs you need to trigger the bug? Ever wanted to interactively see what your static analysis tool was really thinking?

With my collaborators from the University of Tartu (Karoliine Holter, Juhan-Oskar Hennoste, Simmo Saan, Vesal Vojdani), we have an Onward! paper about abstract debugging, where you can "step through" the abstract state of the program, as computed by a static analysis tool.

To appear at Onward! 2024: "Abstract Debuggers: Exploring Program Behaviors Using Static Analysis Results".

https://patricklam.ca/papers/24.onward.abs-debug.pdf

And a special thanks to the SIGPLAN-M mentoring program for matching me with these collaborators!

Hello, Fediverse! We're Kagi, and we're on a mission to create a friendlier, more human-centric internet that has the users' best interest in mind.

Our core product is a search engine that is ad-free, tracking-free, and fully supported by our users. We've worked hard to deliver a high-quality, fast, and reliable search experience without compromising user privacy: https://kagi.com/

Excited to engage with the community here.

#Search #Privacy #AdFree

Absolute funniest TikTok trend in history went down this weekend. Someone posted about this “ATM glitch” they found. They went on to explained that you can deposit checks into ATMs and some of the money becomes available for withdrawal immediately, so you can write fake checks, deposit them, then withdraw the money before the check clears.

They made it sound like some kind of life hack and I guess most of TikTok is too young to know what check fraud is, so they had like hundreds of people uploading videos of themselves writing and depositing fraudulent checks into their own bank accounts tied to their real identities 💀

@soatok @duxsco @filippo @mbmcloughlin The flaw was fixed in firmware 5.7, which is also the firmware that added Ed25519 support to PIV. So the mitigation for vulnerable YubiKeys can't be Ed25519 for the PIV applet as it doesn't exist there.

Between that and explaining the difference between ECC and ECDSA to users, I'm not surprised they just say "use RSA".

Saying the quiet part out loud

https://futurism.com/the-byte/openai-copyrighted-material-parliament

The YubiKey 5, the most widely used hardware token for two-factor authentication based on the FIDO standard, contains a cryptographic flaw that makes the finger-size device vulnerable to cloning when an attacker gains brief physical access to it, researchers said Tuesday.

The cryptographic flaw, known as a side channel, resides in a small microcontroller that’s used in a vast number of other authentication devices, including smartcards used in banking, electronic passports, and the accessing of secure areas. While the researchers have confirmed all YubiKey 5 series models can be cloned, they haven’t tested other devices using the microcontroller, which is SLE78 made by Infineon and successor microcontrollers known as the Infineon Optiga Trust M and the Infineon Optiga TPM. The researchers suspect that any device using any of these three microcontrollers and the Infineon cryptographic library contains the same vulnerability.

https://arstechnica.com/security/2024/09/yubikeys-are-vulnerable-to-cloning-attacks-thanks-to-newly-discovered-side-channel/