From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] add tools/compare-cvelists.sh
Date: Sun, 23 Feb 2025 14:08:22 +0100
Message-ID: <20250223130822.1677157-1-michael@niedermayer.cc> (raw)
This compares the MITRE CVE list with our webpage security list and
produces a diff, so people can investigate, fix, backport and correct
differences
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
---
tools/compare-cvelists.sh | 11 +++++++++++
1 file changed, 11 insertions(+)
create mode 100755 tools/compare-cvelists.sh
diff --git a/tools/compare-cvelists.sh b/tools/compare-cvelists.sh
new file mode 100755
index 00000000000..db5a198c310
--- /dev/null
+++ b/tools/compare-cvelists.sh
@@ -0,0 +1,11 @@
+#!/bin/bash
+
+wget -q -O cvelist-our-html https://git.ffmpeg.org/gitweb/ffmpeg-web.git/blob_plain/HEAD:/src/security
+wget -q -O cvelist-html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=ffmpeg
+
+grep '>CVE-[0-2][90][0-9][0-9]-[0-9]*<' cvelist-html | sed 's/.*\(CVE-[0-2][90][0-9][0-9]-[0-9]*\)<.*/\1/g' |sort|uniq > cvelist
+tr ', (' "\n" <cvelist-our-html | grep 'CVE-[0-2][90][0-9][0-9]-[0-9]*' | sed 's/.*\(CVE-[0-2][90][0-9][0-9]-[0-9]*\)[^0-9].*/\1/g' | sort | uniq > cvelist-our
+diff -u cvelist-our cvelist > cvelist.diff
+diffstat cvelist.diff
+echo please make sure CVE numbers added to our security page have been or will be backported
+echo see cvelist.diff, delete cvelist cvelist.diff cvelist-html cvelist-our cvelist-our-html to cleanup
--
2.48.1
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2025-02-23 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250223130822.1677157-1-michael@niedermayer.cc \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git