public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: apr is in need of an update
Date: Thu, 12 Sep 2024 09:09:00 +0000	[thread overview]
Message-ID: <5d1598c6-d2c7-4630-b7db-2d7ae80859cb@ipfire.org> (raw)

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

Hello development folks,

as I am currently struggling to get my local build environment in a functional state again,
I'd like to flag it here that the Apache Portable Runtime (apr) is in need of an update.

Version 1.7.5 fixes CVE-2023-49582, a flaw potentially allowing local users to read named
shared memory segments. While this doesn't sound overly alarming, my understanding is that
since APR is relatively close to the untrusted outside, it might beneficial to update it
sooner rather than later (and I don't exactly know when the merge window for C189 closes).

If somebody is already working on this, please excuse the noise. If not, I can take care of
it, provided that I am able to build again on my local machine before departing to London. :-)

Thanks, and best regards,
Peter Müller

             reply	other threads:[~2024-09-12  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  9:09 Peter Müller [this message]
2024-09-12 12:46 ` Adolf Belka

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=5d1598c6-d2c7-4630-b7db-2d7ae80859cb@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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