CVE-2018-9305: High severity exiv2 exiv2 vulnerability

Published Apr 4, 2018
·
Updated

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.

Other sources

In Exiv2 0.26, an out-of-bounds read in IptcData::printStructure in iptc.cpp could result in a crash or information leak, due to use of the untrusted len value without any check.

References: https://github.com/Exiv2/exiv2/issues/263 https://github.com/xiaoqx/pocs/blob/master/exiv2/readme.md

Red Hat

Affected Software

1 affected component
exiv2 exiv2<0.26

Event History

Apr 4, 2018
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Data Sourced
via NVD·09:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 12, 2018
Data Sourced
via Red Hat·09:35 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2018-9305?

CVE-2018-9305 is considered to have medium severity due to the potential for crashes and information leaks.

2

How do I fix CVE-2018-9305?

To fix CVE-2018-9305, update Exiv2 to the latest version beyond 0.26 that addresses this vulnerability.

3

What systems are affected by CVE-2018-9305?

CVE-2018-9305 affects Exiv2 versions prior to 0.26.

4

What are the potential consequences of CVE-2018-9305?

The potential consequences of CVE-2018-9305 include application crashes and exposure of sensitive information.

5

Is CVE-2018-9305 easy to exploit?

Exploitation of CVE-2018-9305 may require specific inputs to trigger the out-of-bounds read, making it moderately difficult to exploit.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203