Gpac: Reachable Assertion
CVE-2022-29339 is a high-severity reachable assertion vulnerability in Gpac, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2022-04-12 as the first without the flaw, so updating Gpac to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.19% chance of exploitation within 30 days, higher than 69% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Gpac to 2022-04-12 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | NVD |
Official description
In GPAC 2.1-DEV-rev87-g053aae8-master, function BS_ReadByte() in utils/bitstream.c has a failed assertion, which causes a Denial of Service. This vulnerability was fixed in commit 9ea93a2.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Reachable Assertion
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
How developers prevent this class of flaw
- If the assertion statement is required (e.g., for security or reliability), change the invoking code to avoid the conditions that trigger the assertion.
- Consider changing the assertion to some other less fatal error. This might not be easy to implement, since other code may be needed to handle the error.
- Make sensitive open/close operations non-reachable from directly user-controlled data (e.g. open/close resources)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/gpac/gpac/commit/9ea93a2ec8f555ceed1ee27294cf94822f14f10fThird Party Advisory
Technical write-ups (may include proof of concept)
- github.com/gpac/gpac/issues/2165Exploit, Issue Tracking, Third Party Advisory
Other vulnerabilities in Gpac
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
Recent Reachable Assertion vulnerabilities
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.