From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH] fftools/ffprobe: Fix hypothetical stack buffer overflow Date: Mon, 31 Mar 2025 10:13:16 +0200 Message-ID: <AS8P250MB0744E605D056B1E7058E0D3D8FAD2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw) [-- Attachment #1: Type: text/plain, Size: 27 bytes --] Patch attached. - Andreas [-- Attachment #2: 0001-fftools-ffprobe-Fix-hypothetical-stack-buffer-overfl.patch --] [-- Type: text/x-patch, Size: 988 bytes --] From 5cdf81c1ccd02ed02ed3d99f75e115f2984268b2 Mon Sep 17 00:00:00 2001 From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> Date: Mon, 31 Mar 2025 10:01:07 +0200 Subject: [PATCH] fftools/ffprobe: Fix hypothetical stack buffer overflow It can't really happen, because no currently used pixel format has a name exceeding the size of the buffer. Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> --- fftools/ffprobe.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c index ccc046c560..8db4b47efb 100644 --- a/fftools/ffprobe.c +++ b/fftools/ffprobe.c @@ -2669,7 +2669,8 @@ static void print_pixel_format(WriterContext *w, enum AVPixelFormat pix_fmt) while (s[i] && s[i] == s2[i]) i++; - memcpy(buf, s, FFMIN(sizeof(buf) - 1, i)); + i = FFMIN(sizeof(buf) - 1, i); + memcpy(buf, s, i); buf[i] = '\0'; print_str ("pix_fmt", buf); -- 2.45.2 [-- Attachment #3: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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".
next reply other threads:[~2025-03-31 8:13 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-31 8:13 Andreas Rheinhardt [this message] 2025-04-02 14:22 ` Andreas Rheinhardt
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=AS8P250MB0744E605D056B1E7058E0D3D8FAD2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \ --to=andreas.rheinhardt@outlook.com \ --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