| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GPAC up to 2.2. It has been classified as problematic. Affected by this issue is some unknown functionality. The manipulation leads to divide by zero. This vulnerability is documented as CVE-2023-4678. The attack needs to be performed locally. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in GPAC up to 2.2. It has been rated as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a divide by zero vulnerability. Using CWE to declare the problem leads to CWE-369. The product divides a value by zero. Impacted is availability.
The weakness was released 08/31/2023. The advisory is shared at huntr.dev. The identification of this vulnerability is CVE-2023-4678 since 08/31/2023. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.3-DEV eliminates this vulnerability. Applying the patch 4607052c482a51dbdacfe1ade10645c181d07b07 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://github.com/gpac/gpac/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.6
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 5.1
CNA Vector (huntr.dev): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Divide by zeroCWE: CWE-369 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: GPAC 2.3-DEV
Patch: 4607052c482a51dbdacfe1ade10645c181d07b07
Timeline
08/31/2023 🔍08/31/2023 🔍
08/31/2023 🔍
09/27/2023 🔍
Sources
Product: github.comAdvisory: 4607052c482a51dbdacfe1ade10645c181d07b07
Status: Confirmed
CVE: CVE-2023-4678 (🔍)
GCVE (CVE): GCVE-0-2023-4678
GCVE (VulDB): GCVE-100-238481
Entry
Created: 08/31/2023 19:46Updated: 09/27/2023 16:05
Changes: 08/31/2023 19:46 (49), 09/27/2023 16:00 (1), 09/27/2023 16:05 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.