I'm trying to get more serious about actually writing #AttackerKB analyses of things that catch my interest. Here's my writeup of #pr_pack mule which is totally the name of this vuln, h/t to @dreadpir8robots .
All right #infosec mastodon. How do I find out who is talking about a particular fresh vuln? I’m going to throw out some hashtags and see what turns up relevant conversation.
#186f495d4be1
#cve_2022_23093
#pingbof
#pr_pack
#freebsd
Is this a big deal because stack based #bof in a common #setuid binary, or a #shrug because #ping is capability restricted in #freebsd?
https://www.freebsd.org/security/advisories/FreeBSD-SA-22:15.ping.asc
#infosec #186f495d4be1 #cve_2022_23093 #pingbof #pr_pack #freebsd #bof #setuid #shrug #ping
freebsd.org/security/advisories/FreeBSD-SA-22:15.ping.asc
I don't get why people laughed at this CVE (2022-23093).
I initially misread it and took it for a DoS.
I assume an ICMP fragmentation attack could actually DoS it as well (am I wrong here? tell me why), but this actually could RCE from what I understand.
Am I missing something?
#infosec #security #exploitation #exploitsdev #186f495d4be1 #cve_2022_23093 #pingbof #pr_pack