Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] fuzzer and security issues
Date: Fri, 8 Aug 2025 13:57:20 +0200
Message-ID: <20250808115720.GF29660@pb2> (raw)
In-Reply-To: <20250806103624.GW29660@pb2>


[-- Attachment #1.1: Type: text/plain, Size: 1192 bytes --]

Hi

On Wed, Aug 06, 2025 at 12:36:24PM +0200, Michael Niedermayer wrote:
> Hi all
> 
> theres been a surge of new issues being reported in recent days.
> And its affecting release schedule a bit
> 
> People having access to ffmpeg-security or ossfuzz, are welcome to
> help with fixing them.
> (general rule is check ML for the testcase filename, before working on a case
>  or just ask me on IRC if iam working on a specific issue
>  we will have to figure out how to best coordinate)
> 
> People who want to help but have no access, mail me or send me a private message on irc

some statistics:

we have 17 open security vulnerabilities in ossfuzz
    from these several have fixes, one is in an external lib (libopus)

we have 57 open issues (not limited to security) in ossfuzz

Also the rate of new issues seems going up and there are also now
fully AI genrated reports, that is "google big sleep"

This continuous stream of security issues is a factor in the 8.0 release
being late.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Some Animals are More Equal Than Others. - George Orwell's book Animal Farm

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: 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".

      reply	other threads:[~2025-08-08 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 10:36 Michael Niedermayer
2025-08-08 11:57 ` Michael Niedermayer [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=20250808115720.GF29660@pb2 \
    --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