From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 763] New: [SECURITY] Update pcre to 7.9
Date: Wed, 2 Dec 2009 15:46:11 +0000 (UTC) [thread overview]
Message-ID: <bug-763-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=763
Host: i686-linux
Target: arm-softfloat-linux-uclibcgnueabi
Summary: [SECURITY] Update pcre to 7.9
Product: buildroot
Version: unspecified
Platform: PC
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-
2371
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Outdated package
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: gustavo at zacarias.com.ar
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=795)
--> (https://bugs.busybox.net/attachment.cgi?id=795)
[SECURITY] Bump pcre to 7.9
Heap-based buffer overflow in pcre_compile.c in the Perl-Compatible Regular
Expression (PCRE) library 7.7 allows context-dependent attackers to cause a
denial of service (crash) or possibly execute arbitrary code via a regular
expression that begins with an option and contains multiple branches.
Bump package to version 7.9, remove redundant INSTALL_TARGET and remove
/usr/bin/pcre-config from target.
Should probably remove /usr/bin/pcretest and /usr/bin/pcregrep from target too
for a small size saving.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-12-02 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 15:46 bugzilla at busybox.net [this message]
2009-12-06 15:30 ` [Buildroot] [Bug 763] [SECURITY] Update pcre to 7.9 bugzilla at busybox.net
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=bug-763-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.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