Mark Esler

[Mark Esler @markesler]

Here is my favorite of Christophe's two designs, and the pixel art.

[Mark Esler @markesler]

I would like to thank and recommend @christophesz Christophe Szpajdel for metal logo design 🔥🤘

[Mark Esler @markesler]

My team prefixes [security-crew] to our mailing list, and Christophe designed a logo for those characters. For the back of the shirt, I re-modified pixel art of defending angels slaying demons and shared it with Christophe. He knew exactly what I was looking!

[Mark Esler @markesler]

... CVE-2025-0203 CVE-2025-0204 CVE-2025-0205 CVE-2025-0206 CVE-2025-0207 CVE-2025-0208 CVE-2025-0228 CVE-2025-0229 CVE-2025-0230 CVE-2025-0295 CVE-2025-0296 CVE-2025-0297 CVE-2025-0298 CVE-2025-0299 CVE-2025-0300 CVE-2025-0301

[Mark Esler @markesler]

A researcher from @VulnCheckAI noticed out that the below domains are all being used to generate CVEs.

My hunch is that someone is farming CVEs from @vuldb and @MITREcorp. Both have assigned ~500 CVEs for these "projects".

[Mark Esler @markesler]

For context, #VulDB have already assigned 29 bogus CVEs to https://t.co/6owbOrPmse for 2025.

CVE-2025-0168 CVE-2025-0171 CVE-2025-0172 CVE-2025-0174 CVE-2025-0175 CVE-2025-0176 CVE-2025-0195 CVE-2025-0196 CVE-2025-0197 CVE-2025-0198 CVE-2025-0199 CVE-2025-0200 CVE-2025-0201 ...

[Mark Esler @markesler]

Rsync remote code execution and related vulnerability fixes available https://t.co/eH4RtXKXgo #ubuntu

[Mark Esler @markesler]

@pwningsystems @sirdarckcat @h2hconference Thank you \o/

[Mark Esler @markesler]

@spendergrsec The feels appropriate if BlueZ agrees to use Kernel as a CNA.

( CVE's don't specifying *requiring* CPE, or CVSS, or even a useful description )

[Mark Esler @markesler]

@spendergrsec Have you requested a revocation?

If the Kernel CNA doesn't respond or revoke, raise this to their root/lr-root CNA. And if they don't address it, the Secretariat of the CVE Program.

Keep an eye on https://t.co/Y0apPHShvg

[Mark Esler @markesler]

The “pesky pipe” attack from RFP’s Phrack 55 article (1999) was recently used twenty-five years later in Qualys’ LPE in needrestart disclosure (2024):
https://t.co/1xdIpDo59h

[Mark Esler @markesler]

@spendergrsec indeed https://t.co/N16LQBHxGc

[Qualys @qualys]

The Qualys Threat Research Unit (TRU) has discovered five vulnerabilities. These vulnerabilities can be exploited by any unprivileged user to gain full root access without requiring user interaction. Read about TRU's discovery in our #blog. https://t.co/fMGIqNVeHD #needrestart

[Eduardo Vela @sirdarckcat]

Giving a talk later today @linuxplumbers about kernelCTF and mitigations! We had to upload the slides before the talk, so sharing them here too because why not ;-P https://t.co/XHYLCJfTR6

[Mark Esler @markesler]

Great write-up by Rory McNamara (@PsychoMario) for @snyksec on a root privilege escalation toolchain which leverages DBus, CUPS, and WPA on Ubuntu: https://t.co/f7B1nHHL3G

[Mark Esler @markesler]

@spendergrsec @evilsocket @daveaitel @grsecurity This is good advice, but if this is not public I would work with upstream and distro security teams first. If they take no action, you can always disclose to distros later. The issue with distros is that you want a patch in hand, since there is a 14 day maximum disclosure period.