2 FPE in MP4Box in gpac/gpac

Valid

Reported on

Oct 11th 2023

Description

2 FPE in MP4Box

Version

$ ./MP4Box -version
MP4Box - GPAC version 2.3-DEV-rev566-g50c2ab06f-master

Platform

$ uname -a
Linux user-GE40-2PC-Dragon-Eyes 6.2.0-33-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep  7 10:33:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Reproduce

./MP4Box -dash 10000 poc

Credit

Gandalf4a

Impact

This vulnerability allows a remote attacker to cause a denial of service on an affected gpac MP4Box. Exploiting this vulnerability requires user interaction, as the target must access a malicious page or open a malicious file.

We are processing your report and will contact the gpac team within 24 hours. 2 months ago

A GitHub Issue asking the maintainers to create a SECURITY.md exists 2 months ago

We have contacted a member of the gpac team and are waiting to hear back 2 months ago

A gpac/gpac maintainer

commented 2 months ago

Maintainer

https://github.com/gpac/gpac/issues/2637

A gpac/gpac maintainer modified the Severity from Medium (5.1) to Medium (4) 2 months ago

The researcher has received a minor penalty to their credibility for miscalculating the severity: -1

A gpac/gpac maintainer validated this vulnerability 2 months ago

gandalf4a has been awarded the disclosure bounty

The fix bounty is now up for grabs

The researcher's credibility has increased: +7

A gpac/gpac maintainer marked this as fixed in 2.3.0-DEV with commit 50a60b 2 months ago

The fix bounty has been dropped

This vulnerability will not receive a CVE

A gpac/gpac maintainer published this vulnerability 2 months ago

gandalf4a

commented 2 months ago

Researcher

Can this vulnerability be applied for cve? @admin

Ben Harvie

commented 2 months ago

Admin

CVE assignment is the maintainers decision, if we can get confirmation from them I can assign a CVE. Thanks!

gandalf4a

commented 2 months ago

Researcher

The maintainers didn't seem to know how to do it, they were confirmed directly in the github issue(https://github.com/gpac/gpac/issues/2637). Can we assign a CVE through this? Thanks! @admin

to join this conversation

We are processing your report and will contact the gpac team within 24 hours. 2 months ago

A GitHub Issue asking the maintainers to create a SECURITY.md exists 2 months ago

We have contacted a member of the gpac team and are waiting to hear back 2 months ago

A gpac/gpac maintainer

commented 2 months ago

Maintainer

https://github.com/gpac/gpac/issues/2637

A gpac/gpac maintainer modified the Severity from Medium (5.1) to Medium (4) 2 months ago

The researcher has received a minor penalty to their credibility for miscalculating the severity: -1

A gpac/gpac maintainer validated this vulnerability 2 months ago

gandalf4a has been awarded the disclosure bounty

The fix bounty is now up for grabs

The researcher's credibility has increased: +7

A gpac/gpac maintainer marked this as fixed in 2.3.0-DEV with commit 50a60b 2 months ago

The fix bounty has been dropped

This vulnerability will not receive a CVE

A gpac/gpac maintainer published this vulnerability 2 months ago

gandalf4a

commented 2 months ago

Researcher

Can this vulnerability be applied for cve? @admin

Ben Harvie

commented 2 months ago

Admin

CVE assignment is the maintainers decision, if we can get confirmation from them I can assign a CVE. Thanks!

gandalf4a

commented 2 months ago

Researcher

The maintainers didn't seem to know how to do it, they were confirmed directly in the github issue(https://github.com/gpac/gpac/issues/2637). Can we assign a CVE through this? Thanks! @admin

to join this conversation