bfabiszewski Libmobi up to 0.10 null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in bfabiszewski Libmobi up to 0.10. This vulnerability affects unknown code. This manipulation causes null pointer dereference. This vulnerability is handled as CVE-2022-2279. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic was found in bfabiszewski Libmobi up to 0.10. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:
NULL Pointer Dereference in GitHub repository bfabiszewski/libmobi prior to 0.11.
The weakness was released 07/01/2022. The advisory is shared at huntr.dev. This vulnerability is known as CVE-2022-2279. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.11 eliminates this vulnerability. Applying the patch c0699c8693c47f14a2e57dec7292e862ac7adf9c 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
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 6.6
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
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: Libmobi 0.11
Patch: c0699c8693c47f14a2e57dec7292e862ac7adf9c
Timeline
07/01/2022 🔍07/01/2022 🔍
07/01/2022 🔍
07/17/2022 🔍
Sources
Product: github.comAdvisory: c0699c8693c47f14a2e57dec7292e862ac7adf9c
Status: Confirmed
CVE: CVE-2022-2279 (🔍)
GCVE (CVE): GCVE-0-2022-2279
GCVE (VulDB): GCVE-100-203041
Entry
Created: 07/01/2022 12:35Updated: 07/17/2022 11:46
Changes: 07/01/2022 12:35 (40), 07/17/2022 11:38 (2), 07/17/2022 11:46 (28)
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.