From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"steve@sakoman.com" <steve@sakoman.com>
Subject: Re: [OE-core] cups: whitelist CVE-2018-6553
Date: Wed, 18 Nov 2020 23:56:38 +0000 [thread overview]
Message-ID: <8df909f90903613c2aa74e2b43dec9d747b5330a.camel@intel.com> (raw)
In-Reply-To: <20201118152522.20849-1-steve@sakoman.com>
On Wed, 2020-11-18 at 05:25 -1000, Steve Sakoman wrote:
> This an Ububtu specific issue:
>
> The CUPS AppArmor profile incorrectly confined the dnssd backend
> due to use of hard links. A local attacker could possibly use this
> issue to escape confinement. This flaw affects versions prior to
> 2.2.7-1ubuntu2.1 in Ubuntu 18.04 LTS, prior to 2.2.4-7ubuntu3.1
> in Ubuntu 17.10, prior to 2.1.3-4ubuntu0.5 in Ubuntu 16.04 LTS,
> and prior to 1.7.2-0ubuntu1.10 in Ubuntu 14.04 LTS
It doesn't affect the default configuration but someone in theory could
have extended the recipe to have AppArmor support and then it might be
vulnerable?
Since this CVE is sort of distro specific and not package specific,
should this be part of recipe or the poky distro meta data?
Thanks,
Anuj
>
> Signed-off-by: Steve Sakoman <steve@sakoman.com>
> ---
> meta/recipes-extended/cups/cups.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-extended/cups/cups.inc b/meta/recipes-
> extended/cups/cups.inc
> index 87870e4aba..df8d4d284a 100644
> --- a/meta/recipes-extended/cups/cups.inc
> +++ b/meta/recipes-extended/cups/cups.inc
> @@ -20,6 +20,9 @@ SRC_URI = "
> https://github.com/apple/cups/releases/download/v${PV}/${BP}-source.t
> UPSTREAM_CHECK_URI = "https://github.com/apple/cups/releases"
> UPSTREAM_CHECK_REGEX = "cups-(?P<pver>\d+\.\d+(\.\d+)?)-source.tar"
>
> +# This is an Ubuntu only issue.
> +CVE_CHECK_WHITELIST += "CVE-2018-6553"
> +
> LEAD_SONAME = "libcupsdriver.so"
>
> CLEANBROKEN = "1"
>
>
>
next prev parent reply other threads:[~2020-11-18 23:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 15:25 [OE-core] cups: whitelist CVE-2018-6553 Steve Sakoman
2020-11-18 23:56 ` Anuj Mittal [this message]
2020-11-19 0:12 ` Steve Sakoman
2020-11-19 8:46 ` Mikko Rapeli
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=8df909f90903613c2aa74e2b43dec9d747b5330a.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.com \
/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