Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marvin Scholz <epirat07-at-gmail.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2 1/3] lavf/rtpdec: fix RTCP SR packet length check
Date: Fri, 04 Jul 2025 17:17:48 +0200
Message-ID: <57B7B3CD-F138-42B0-906B-0E78F9F39AE1@gmail.com> (raw)
In-Reply-To: <20250628142725.26651-1-epirat07@gmail.com>



On 28 Jun 2025, at 16:27, Marvin Scholz wrote:

> The minimum valid packet length is 28, given that the length includes
> the packet header.
>
> This didn't cause any issues so far as the code did not care about the
> last two fields in the SR section, but will be relevant in a future
> commit.
> ---
>  libavformat/rtpdec.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/rtpdec.c b/libavformat/rtpdec.c
> index d54ac31eb0..5aecf7fbc7 100644
> --- a/libavformat/rtpdec.c
> +++ b/libavformat/rtpdec.c
> @@ -187,7 +187,7 @@ static int rtcp_parse_packet(RTPDemuxContext *s, const unsigned char *buf,
>
>          switch (buf[1]) {
>          case RTCP_SR:
> -            if (payload_len < 20) {
> +            if (payload_len < 28) {
>                  av_log(s->ic, AV_LOG_ERROR, "Invalid RTCP SR packet length\n");
>                  return AVERROR_INVALIDDATA;
>              }
> -- 
> 2.39.5 (Apple Git-154)

If there are no objections, I plan to push this patchset start of next week.
_______________________________________________
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".

      parent reply	other threads:[~2025-07-04 15:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 18:02 [FFmpeg-devel] [PATCH " Marvin Scholz
2025-06-24 18:02 ` [FFmpeg-devel] [PATCH 2/3] lavf: add and use AVRTCPSenderReport struct Marvin Scholz
2025-06-27 21:50   ` Michael Niedermayer
2025-06-28 14:28     ` Marvin Scholz
2025-06-24 18:02 ` [FFmpeg-devel] [PATCH 3/3] lavf: add AV_PKT_DATA_RTCP_SR side data type Marvin Scholz
2025-06-28 14:27 ` [FFmpeg-devel] [PATCH v2 1/3] lavf/rtpdec: fix RTCP SR packet length check Marvin Scholz
2025-06-28 14:27   ` [FFmpeg-devel] [PATCH v2 2/3] lavf: add and use AVRTCPSenderReport struct Marvin Scholz
2025-06-28 14:27   ` [FFmpeg-devel] [PATCH v2 3/3] lavf: add AV_PKT_DATA_RTCP_SR side data type Marvin Scholz
2025-07-04 15:17   ` Marvin Scholz [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=57B7B3CD-F138-42B0-906B-0E78F9F39AE1@gmail.com \
    --to=epirat07-at-gmail.com@ffmpeg.org \
    --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