From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libpjsip: security bump to version 2.14
Date: Sun, 03 Dec 2023 22:22:21 +0100 [thread overview]
Message-ID: <87h6kzvv5e.fsf@48ers.dk> (raw)
In-Reply-To: <20231201212318.1091953-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Fri, 1 Dec 2023 22:23:18 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix CVE-2023-38703: PJSIP is a free and open source multimedia
> communication library written in C with high level API in C, C++, Java,
> C#, and Python languages. SRTP is a higher level media transport which
> is stacked upon a lower level media transport such as UDP and ICE.
> Currently a higher level transport is not synchronized with its lower
> level transport that may introduce use-after-free issue. This
> vulnerability affects applications that have SRTP capability
> (`PJMEDIA_HAS_SRTP` is set) and use underlying media transport other
> than UDP. This vulnerability’s impact may range from unexpected
> application termination to control flow hijack/memory corruption. The
> patch is available as a commit in the master branch.
> https://github.com/pjsip/pjproject/security/advisories/GHSA-f76w-fh7c-pc66
> https://github.com/pjsip/pjproject/releases/tag/2.14
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-12-03 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 21:23 [Buildroot] [PATCH 1/1] package/libpjsip: security bump to version 2.14 Fabrice Fontaine
2023-12-02 8:40 ` Peter Korsgaard
2023-12-03 21:22 ` Peter Korsgaard [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=87h6kzvv5e.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=luca.ceresoli@bootlin.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