From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: madwifi_ng: security issue, CVE-2006-6332
Date: Sun, 17 Dec 2006 11:00:55 +1100 [thread overview]
Message-ID: <20061217000055.GA30417@twibble.org> (raw)
Anyone using madwifi should upgrade to r1844-20061208 to get the fix for
CVE-2006-6332. From the announcement on madwifi.org:
Release 0.9.2.1 fixes critical security issue
A critical security flaw (CVE-2006-6332) has been discovered which can be
exploited from remote and allows arbitrary code injection. The fix has been
committed to trunk in r1842. In addition, we released v0.9.2.1 (v0.9.2 plus
the fix for the issue), which is available for download from sf.net.
All users should upgrade as soon as possible.
----- Forwarded message from "\"lenehan commit\"" <openembedded-commits@lists.openembedded.org> -----
From: openembedded-commits@lists.openembedded.org ("lenehan commit")
Subject: [oe-commits] org.oe.dev madwifi-ng r1844: Add svn snapshot 1844
which is the same as the 0.9.2.1
Date: Sun, 17 Dec 2006 00:58:12 +0100
madwifi-ng r1844: Add svn snapshot 1844 which is the same as the 0.9.2.1
release. This includes a critical fix for CVE-2006-6332 which is a remotely
exploitable stack-based buffer overflow bug.
Author: lenehan@openembedded.org
Branch: org.openembedded.dev
Revision: af1d7cf6768b5e5205f07a7a63b6767971ccb1b7
ViewMTN: http://monotone.openembedded.org/revision.psp?id=af1d7cf6768b5e5205f07a7a63b6767971ccb1b7
Files:
1
packages/madwifi/madwifi-ng-r1844-20061208
packages/madwifi/madwifi-ng-r1844-20061208/10-xscale-be-elf-copts.patch
packages/madwifi/madwifi-ng-r1844-20061208/10-xscale-le-elf-copts.patch
packages/madwifi/madwifi-ng_r1844-20061208.bb
[...]
----- End forwarded message -----
--
Jamie Lenehan <lenehan@twibble.org>
reply other threads:[~2006-12-17 0:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061217000055.GA30417@twibble.org \
--to=lenehan@twibble.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.