| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Exiv2 0.26. This issue affects the function IptcData::printStructure of the file iptc.c. Executing a manipulation can lead to out-of-bounds.
The identification of this vulnerability is CVE-2018-9306. The attack may be launched remotely. There is no exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability has been found in Exiv2 0.26 (Image Processing Software) and classified as critical. This vulnerability affects the function IptcData::printStructure of the file iptc.c. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
In Exiv2 0.26, an out-of-bounds read in IptcData::printStructure in iptc.c could result in a crash or information leak, related to the "!= 0x1c" case.
The bug was discovered 04/04/2018. The weakness was shared 04/04/2018 (Website). The advisory is available at github.com. This vulnerability was named CVE-2018-9306 since 04/04/2018. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 119134 (GLSA-201811-14 : Exiv2: Multiple vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks and running in the context l.
Upgrading eliminates this vulnerability. A possible mitigation has been published 9 months after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (119134). The entries VDB-113170, VDB-114989, VDB-114990 and VDB-115290 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
Website
- Product: https://github.com/Exiv2/exiv2/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 119134
Nessus Name: GLSA-201811-14 : Exiv2: Multiple vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
04/04/2018 🔍04/04/2018 🔍
04/04/2018 🔍
04/05/2018 🔍
11/24/2018 🔍
11/26/2018 🔍
02/27/2023 🔍
Sources
Product: github.comAdvisory: 263
Status: Not defined
CVE: CVE-2018-9306 (🔍)
GCVE (CVE): GCVE-0-2018-9306
GCVE (VulDB): GCVE-100-115834
See also: 🔍
Entry
Created: 04/05/2018 10:39Updated: 02/27/2023 08:03
Changes: 04/05/2018 10:39 (37), 01/22/2020 13:12 (17), 02/09/2021 07:23 (8), 02/27/2023 08:03 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.