libvips up to 8.7.3 iofuncs/memory.c resource management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in libvips up to 8.7.3. Affected is an unknown function of the file iofuncs/memory.c. The manipulation results in resource management. This vulnerability is reported as CVE-2019-6976. The attack can be launched remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in libvips up to 8.7.3. It has been classified as problematic. Affected is some unknown functionality of the file iofuncs/memory.c. The manipulation with an unknown input leads to a resource management vulnerability. CWE is classifying the issue as CWE-399. This is going to have an impact on availability. CVE summarizes:
libvips before 8.7.4 writes to uninitialized memory locations in unspecified error cases because iofuncs/memory.c does not zero out allocated memory.
The bug was discovered 01/18/2019. The weakness was disclosed 01/26/2019 (Website). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2019-6976 since 01/26/2019. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 8 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 8.7.4 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
License
Website
- Product: https://github.com/libvips/libvips/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
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: Resource managementCWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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: libvips 8.7.4
Patch: github.com
Timeline
01/18/2019 🔍01/26/2019 🔍
01/26/2019 🔍
01/26/2019 🔍
01/27/2019 🔍
07/03/2023 🔍
Sources
Product: github.comAdvisory: 00622428bda8d7521db8d74260b519fa41d69d0a
Status: Not defined
CVE: CVE-2019-6976 (🔍)
GCVE (CVE): GCVE-0-2019-6976
GCVE (VulDB): GCVE-100-130272
Entry
Created: 01/27/2019 16:13Updated: 07/03/2023 14:49
Changes: 01/27/2019 16:13 (57), 05/06/2020 11:46 (1), 07/03/2023 14:49 (6)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.