Raphaël Rigo

Security stuff.

Raphaël Rigo boosted:
2026-02-13

Greetings and welcome to today's #nakeddiefriday installment.

Today's guest is a smartcard chip, for which I do not know the actual p/n -- only it's die marking: M7690-G1, by Infineon. This came from a SIM card. The chip had polyimide on top which had to be stripped off, hence the damage on some top metal.

Unfortunately, power distribution routing and CMP dummy fill obstructs the majority of the detail. 🧵

#electronics #reverseengineering #icre #smartcard

Die overview shot. Upper half of the die is occupied with a variety of stuff, while lower half is filled with the dummy pattern on top metal.
Raphaël Rigo boosted:
2026-02-13

2026, the year of the AI-driven attacker that could do back flips, they said.

Meanwhile, there's a magic number that allows Auth Bypass against Ivanti EPM (CVE-2026-1603)

something about a pledge 🙄

Raphaël Rigo boosted:
2026-02-11

They finally did it. Microsoft has successfully over-engineered a text editor into a threat vector.

This CVE is an 8.8 severity RCE in Notepad of all things lmao.

Apparently, the "innovation" of adding markdown support came with the ability of launching unverified protocols that load and execute remote files.

We have reached a point where the simple act of opening a .md file in a native utility can compromise your system. Is nothing safe anymore? 😭

msrc.microsoft.com/update-guid

#noai #microslop #microsoft #windows #programming #writing #windows11 #enshittification #cybersecurity #infosec #technology

screenshot from the CVE page
Raphaël Rigo boosted:
Zack Whittakerzackwhittaker
2026-02-08

NEW: A few weeks ago, @PogoWasRight and I ran a survey asking security researchers and journalists about the legal and criminal threats they have received for doing their jobs.

Over 100 people responded, and we now have our results.

One of our key findings is that while legal threats and criminal threats are common, most researchers & journalists stood their ground and did not give in to threats.

More: this.weekinsecurity.com/new-su

Results: databreaches.net/2026/02/02/un

PDF: databreaches.net/wp-content/up

Raphaël Rigo boosted:
2026-02-06

Hello! It has been a little while, but #nakeddiefriday is back in town.

Today's exhibit is an old PIC1650A. Yes, one of *the* PIC series of microcontrollers. Note it was designed by General Instrument in 1980. It was fabbed in a single metal layer, metal-gate NMOS process. The image is about 4.3x3.8 mm.

No full-res link as SP is still borked.

#electronics #reverseengineering #icre

Die overview shot
Raphaël Rigo boosted:
2026-02-03

“The uncomfortable truth: every #phone with a SIM card is a tracking device that happens to run apps.”

fumics.in/posts/2026-02-01-pho

2026-02-03

@pinkflawd
Add some nice AT&T syntax over it and

movl    %eax, (%esp)

AAAAaaaaaaaaaaaaaAAAAAAah.

Raphaël Rigo boosted:
2026-02-01
@XC3LL Thanks for posting this, great to see someone has the guts to say the emperor is naked!

My 2c:
- Red Teams should be about the "difficult" things you mention at the end IMO. Spending resources on initial access is mostly pointless (from the client's perspective, finding 0d is always cool ofc) when a new blinky box exploit, leaked code signing cert, etc. is popping up every other week. IME many clients pay for (bad) initial access simulations because organizing assumed breach in-house is hard.
- A way to burst the bubbles you describe is to mandate scenarios based on real-world threat intel. But this works against intial access again, because RT's can't scale their R&D as black hats do (attack surface is clients vs the Internet).
Raphaël Rigo boosted:
Juanma FernandezXC3LL
2026-02-01

A small rant:

The State of Art in Red Team is whatever you want to believe

x-c3ll.github.io/posts/Rant-Re

Raphaël Rigo boosted:
Corsaccorsac
2026-01-29
Raphaël Rigo boosted:
Pass the SALT Conferencepassthesaltcon@infosec.exchange
2026-01-26

📣 Call for proposals for the 2026 edition.

We are looking for talks and workshops about security and open-source software.

Offensive or defensive security, low level, systems or CI management, tooling, we welcome any security subject as long as it related to a free software or provide an open-source tool!

👉 2026.pass-the-salt.org/

📩 A question, doubt? Our support team is listening to you: speaker-support@pass-the-salt.org

⏰ The deadline is March, 31 2026!

Raphaël Rigo boosted:
Gabriele Sveltogabrielesvelto@mas.to
2026-01-25

In the early days of personal computing CPU bugs were so rare as to be newsworthy. The infamous Pentium FDIV bug is remembered by many, and even earlier CPUs had their own issues (the 6502 comes to mind). Nowadays they've become so common that I encounter them routinely while triaging crash reports sent from Firefox users. Given the nature of CPUs you might wonder how these bugs arise, how they manifest and what can and can't be done about them. 🧵 1/31

Raphaël Rigo boosted:

OMG. -froot bug resurfaced. seclists.org/oss-sec/2026/q1/89

I see the headlines, "10 years old bug".

My friends, this bug is older. Much older. Not this particular instance, but it is a classical mistake to make. It's a command line injection when calling the login executable.

Some people point to CVE-2007-0882. Solaris had that, almost 20 years ago.

But it's even older than that. It's so old it predates the CVE system. I don't remember exact dates, but we popped Linux and AIX boxes with that, mid 90s.

But it is *even older* than that. Have a look at System V R4, ©1990, getty calling login with unsanitized input:

github.com/calmsacibis995/svr4

But how deep does the rabbit hole go? When was this bug introduced?

Getty called login with user input since the dawn of time (UNIX V2, 1972):

tuhs.org/cgi-bin/utree.pl?file

But this predates command line arguments in login:

tuhs.org/cgi-bin/utree.pl?file

So, when did this particular command line feature of login appear?

In the BSD universe, -f was introduced with POSIX compatibilitiy in 4.3BSD-Reno:

tuhs.org/cgi-bin/utree.pl?file

But someone paid attention and filtered out user names starting with - in getty:

tuhs.org/cgi-bin/utree.pl?file

RCS timestamp says 6/29/1990, so same age as SysV R4.

The original 4.3BSD (1986) doesn't filter the user name:

tuhs.org/cgi-bin/utree.pl?file

And it does have a -r option in login:

tuhs.org/cgi-bin/utree.pl?file

Exploitable? No idea, argv processing might be a problem. I'll find out another day.

In conclusion: bug existed since 1990, it's so easy to make when implementing POSIX that it keeps resurfacing, and at least one person in Berkeley knew since day 0.

Raphaël Rigo boosted:
2026-01-20

Giving University Exams in the Age of Chatbots

How I managed to give an exam while giving the students the choice to use a chatbot or not.

And what I learned in the process.

ploum.net/2026-01-19-exam-with

Raphaël Rigo boosted:
Randahl Finkrandahl
2026-01-20

This is absolutely awesome! The @leavex campaign now has their website up an running, so we can see exactly which members of the EU parliament still support Musk's disinformation platform X, and avoid voting for them.

I hope @leavex expands to add every national parliament — the disinformation has to end.

Se their excellent overview here:
leavex.eu/politicians/

Please boost this to support the campaign.

Screen shot from the web page you can view when following the link.
2026-01-20

@raptor I initially thought someone made a joke about the infamous Solaris' "-froot" telnetd bug (spinics.net/lists/bugtraq/msg2)
Ooops. no.

Raphaël Rigo boosted:
2026-01-19

L’appel à soumission pour le #sstic2026 est étendu jusqu’à vendredi 23 janvier, 23h59.

sstic.org/2026/news/cfp_2026_p

#sstic #sstic2026

Raphaël Rigo boosted:
2026-01-19
Raphaël Rigo boosted:
Natalie Silvanovichnatashenka@infosec.exchange
2026-01-16

Today, Project Zero released a 0-click exploit chain for the Pixel 9. While it targets the Pixel, the 0-click bug and exploit techniques we used apply to most other Android devices.

projectzero.google/2026/01/pix

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst