ffmpeg: Add "libswresample libavcodec" to CVE_PRODUCT
PATCH 1/1 ffmpeg: Add "libswresample libavcodec" to CVE_PRODUCT
Currently, CVE_PRODUCT only detects vulnerabilities where the product is "ffmpeg".
However, there are also vulnerabilities where the product is "libswresample", and "libavcodec" as shown below.
https://app.opencve.io/vendors/?vendor=ffmpeg
Therefore, add "libswresample libavcodec" to CVE_PRODUCT to detect vulnerabilities where the product is "libswresample libavcodec" as well.
--- meta/recipes-multimedia/ffmpeg/ffmpeg_5.0.1.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-multimedia/ffmpeg/ffmpeg_5.0.1.bb +2 -0
@@ -186,3 +186,5 @@ INSANE_SKIP:${MLPREFIX}libavutil = "textrel" INSANE_SKIP:${MLPREFIX}libswscale = "textrel" INSANE_SKIP:${MLPREFIX}libswresample = "textrel" INSANE_SKIP:${MLPREFIX}libpostproc = "textrel" + +CVE_PRODUCT = "ffmpeg libswresample libavcodec"
Signature · 1 line
2.17.1
Could you also send this patch for master? Since the issue also exists in master, we'll need to fix it there before I can take the patch for the stable branches.
Thanks!
Steve
Quoted 37 lines · On Wed, Oct 16, 2024 at 3:17 AM aszh07 via lists.openembedded.org…
Currently,
CVE_PRODUCTonly detects vulnerabilities where the product is "ffmpeg".However, there are also vulnerabilities where the product is "libswresample", and "libavcodec" as shown below.
https://app.opencve.io/vendors/?vendor=ffmpegTherefore, add "libswresample libavcodec" to
CVE_PRODUCTto detect vulnerabilities where the product is "libswresample libavcodec" as well.Signed-off-by aszh07 <[email protected]>--- meta/recipes-multimedia/ffmpeg/ffmpeg_5.0.1.bb | 2 ++ 1 file changed, 2 insertions(+)meta/recipes-multimedia/ffmpeg/ffmpeg_5.0.1.bb +2
-1@@ -186,3 +186,5 @@ INSANE_SKIP:${MLPREFIX}libavutil = "textrel" INSANE_SKIP:${MLPREFIX}libswscale = "textrel" INSANE_SKIP:${MLPREFIX}libswresample = "textrel" INSANE_SKIP:${MLPREFIX}libpostproc = "textrel" + +CVE_PRODUCT = "ffmpeg libswresample libavcodec" --2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#205961): https://lists.openembedded.org/g/openembedded-core/message/205961
Mute This Topic: https://lists.openembedded.org/mt/109041180/3620601
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Hi Steve,
This changes are already upstreamed to master. It also got integrated to master.
https://git.yoctoproject.org/poky/commit/?id=22c08cab4db89dc3d41ab22cfe0482c1483391dd
Thanks!
Zahir
Hi Steve,
Could you please check why still these changes are not integrated in kirkstone branch?
These changes are already upstreamed to master. It also got integrated to master.
https://git.yoctoproject.org/poky/commit/?id=22c08cab4db89dc3d41ab22cfe0482c1483391dd
Thanks!
Zahir
Hi Steve,
Could you please check why still these changes are not integrated in kirkstone branch?
These changes are already upstreamed to master. It also got integrated to master.
https://git.yoctoproject.org/poky/commit/?id=22c08cab4db89dc3d41ab22cfe0482c1483391dd
Thanks!
Zahir
Quoted 4 lines · On 5/13/25 12:32, aszh07 via lists.openembedded.org wrote:
Hi Steve,
Could you please check why still these changes are not integrated in kirkstone branch?
Try to send the patch once again. In patchwork it seems to be stuck in "waiting for upstream" status, and I suspect it got buried under other things considering that you kept following it up diligently without feedback- a fresh patch will be more visible.
Quoted 16 lines
These changes are already upstreamed to master. It also got integrated to master.
https://git.yoctoproject.org/poky/commit/?id=22c08cab4db89dc3d41ab22cfe0482c1483391ddThanks!
Zahir-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#216410): https://lists.openembedded.org/g/openembedded-core/message/216410
Mute This Topic: https://lists.openembedded.org/mt/109041180/6084445
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-