From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: Remote code execution bug in FreeBSD's ping (CVE-2022-23093)
Date: Thu, 1 Dec 2022 09:18:08 -0800 [thread overview]
Message-ID: <CAA93jw7-48fV4yLQKNECw4cnaLh_mny23PXGUyQeZjyedhDb1Q@mail.gmail.com> (raw)
In-Reply-To: <DM4PR18MB4254443C49D441785E22DF20AB149@DM4PR18MB4254.namprd18.prod.outlook.com>
ping.
---------- Forwarded message ---------
From: Mike Lewinski via NANOG <nanog@nanog.org>
Date: Thu, Dec 1, 2022 at 9:16 AM
Subject: Remote code execution bug in FreeBSD's ping (CVE-2022-23093)
To: nanog@nanog.org <nanog@nanog.org>
Ooof.
https://www.freebsd.org/security/advisories/FreeBSD-SA-22:15.ping.asc
Some hope here: "The ping process runs in a capability mode sandbox on
all affected versions of FreeBSD and is thus very constrainted in how
it can interact with the rest of the system at the point where the bug
can occur."
Lots of other things are based on FreeBSD and may be affected,
including firewalls like pfsense and OPNsense and possibly Junos. At
the least I expect host discovery is ramping up by now.
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2022-12-01 17:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <DM4PR18MB4254443C49D441785E22DF20AB149@DM4PR18MB4254.namprd18.prod.outlook.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7-48fV4yLQKNECw4cnaLh_mny23PXGUyQeZjyedhDb1Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox