Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: Anuj Mittal <anuj.mittal@oss.qualcomm.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][scarthgap][PATCH 4/4] rsyslog: set status for CVE-2015-3243
Date: Mon, 17 Nov 2025 09:52:51 +0100	[thread overview]
Message-ID: <5748b43a-d6a6-482c-850c-5ccb03ecd05f@gmail.com> (raw)
In-Reply-To: <CA+s=J=xgkjKkQ+rC83CALXWCXoWhcj1a7RXbRm68=UTfJm1-wQ@mail.gmail.com>

On 11/17/25 06:50, Anuj Mittal wrote:
>
>
>
> On Sat, Nov 15, 2025 at 9:00 PM Gyorgy Sarvari via
> lists.openembedded.org <http://lists.openembedded.org>
> <skandigraun=gmail.com@lists.openembedded.org> wrote:
>
>     Details: https://nvd.nist.gov/vuln/detail/CVE-2015-3243
>
>     The issue is about file permissions: by default rsyslog creates
>     world-readable
>     files. In case a log message contains some sensitive information,
>     then that's
>     exposed to every user on the system.
>
>     However the rsyslog.conf file that is shipped with the recipe
>     solves it: it
>     already sets non-world-readable default permissions on all files,
>     so this
>     vulnerability is fixed in the default OE recipe.
>
>     See also this package in OpenSuse[1], where it is solved the same way.
>
>     [1]: https://build.opensuse.org/requests/619439/changes
>     (rsyslog.conf.in <http://rsyslog.conf.in>)
>
>     Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
>     ---
>      meta-oe/recipes-extended/rsyslog/rsyslog/rsyslog.conf | 3 ++-
>      meta-oe/recipes-extended/rsyslog/rsyslog_8.2402.0.bb
>     <http://rsyslog_8.2402.0.bb>  | 2 ++
>      2 files changed, 4 insertions(+), 1 deletion(-)
>
>     diff --git a/meta-oe/recipes-extended/rsyslog/rsyslog/rsyslog.conf
>     b/meta-oe/recipes-extended/rsyslog/rsyslog/rsyslog.conf
>     index dbfefb7597..6316efb629 100644
>     --- a/meta-oe/recipes-extended/rsyslog/rsyslog/rsyslog.conf
>     +++ b/meta-oe/recipes-extended/rsyslog/rsyslog/rsyslog.conf
>     @@ -13,7 +13,8 @@ $ModLoad imklog   # kernel logging (formerly
>     provided by rklogd)
>
>      #
>      # Set the default permissions
>     -#
>     +# Setting the $FileCreateMode not world readable fixes CVE-2015-3243
>     +#
>      $FileOwner root
>      $FileGroup adm
>      $FileCreateMode 0640
>     diff --git a/meta-oe/recipes-extended/rsyslog/rsyslog_8.2402.0.bb
>     <http://rsyslog_8.2402.0.bb>
>     b/meta-oe/recipes-extended/rsyslog/rsyslog_8.2402.0.bb
>     <http://rsyslog_8.2402.0.bb>
>     index af46cc14d7..59944cd70c 100644
>     --- a/meta-oe/recipes-extended/rsyslog/rsyslog_8.2402.0.bb
>     <http://rsyslog_8.2402.0.bb>
>     +++ b/meta-oe/recipes-extended/rsyslog/rsyslog_8.2402.0.bb
>     <http://rsyslog_8.2402.0.bb>
>     @@ -37,6 +37,8 @@ SRC_URI[sha256sum] =
>     "acbdd8579489df36b4a383dc6909a61b7623807f0aff54c062115f2de7
>      UPSTREAM_CHECK_URI = "https://github.com/rsyslog/rsyslog/releases"
>      UPSTREAM_CHECK_REGEX = "(?P<pver>\d+(\.\d+)+)"
>
>     +CVE_STATUS[CVE-2015-3243] = "fix-file-included: The shipped
>     default rsyslog.conf contains the fix"
>     +
>
>
>  fix-file-included isn't available in scarthgap so we will have to use
> something else.

Right, it seems there isn't any that would really fit... will pick a
"Patched" status in a few moments.


      reply	other threads:[~2025-11-17  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-15 12:59 [meta-oe][scarthgap][PATCH 1/4] audiofile: patch CVE-2019-13147 and CVE-2022-24599 Gyorgy Sarvari
2025-11-15 12:59 ` [meta-oe][scarthgap][PATCH 2/4] audiofile: patch CVE-2018-13440 and CVE-2018-17059 Gyorgy Sarvari
2025-11-15 12:59 ` [meta-oe][scarthgap][PATCH 3/4] audiofile: mark CVE-2020-18781 as patched Gyorgy Sarvari
2025-11-15 13:00 ` [meta-oe][scarthgap][PATCH 4/4] rsyslog: set status for CVE-2015-3243 Gyorgy Sarvari
2025-11-17  5:50   ` [oe] " Anuj Mittal
2025-11-17  8:52     ` Gyorgy Sarvari [this message]

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=5748b43a-d6a6-482c-850c-5ccb03ecd05f@gmail.com \
    --to=skandigraun@gmail.com \
    --cc=anuj.mittal@oss.qualcomm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox