All of lore.kernel.org
 help / color / mirror / Atom feed
From: "DC" <davidcorbe@outlook.com>
To: openembedded-core@lists.openembedded.org
Subject: [kirkstone][dunfell] CVE-2023-25193 fix request
Date: Thu, 09 Mar 2023 23:29:37 -0800	[thread overview]
Message-ID: <xthe.1678433377646255789.WG7C@lists.openembedded.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

Hi Team,

We are working on CVE-2023-25193 for kirkstone and dunfell branch as it is causing errors in our applications.
There have been previous threads pointing to the issues that backporting is difficult due to code changes and new files being added and there are no second thoughts for the same.

Could you please suggest how can we proceed to fix it ? Version updates is out of scope due to various internal reasons. If anyone can help, it would be great help.

Thanks,

DC

[-- Attachment #2: Type: text/html, Size: 547 bytes --]

             reply	other threads:[~2023-03-10  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  7:29 DC [this message]
2023-03-10  8:20 ` [OE-core] [kirkstone][dunfell] CVE-2023-25193 fix request Polampalli, Archana
2023-03-10  8:32   ` Siddharth
2023-03-23  5:12     ` DC

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=xthe.1678433377646255789.WG7C@lists.openembedded.org \
    --to=davidcorbe@outlook.com \
    --cc=openembedded-core@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.