CVE-2017-9114: Medium severity OpenEXR OpenEXR vulnerability
Published May 21, 2017
·Updated
In OpenEXR 2.2.0, an invalid read of size 1 in the refill function in ImfFastHuf.cpp could cause the application to crash.
Affected Software
2 affected componentsFixes available
debian/openexr
2.2.1-4.1+deb10u12.2.1-4.1+deb10u22.5.4-2+deb11u13.1.5-53.1.5-5.1
OpenEXR OpenEXR=2.2.0
Event History
May 21, 2017
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2017-9114?
CVE-2017-9114 has a high severity due to the potential application crash caused by an invalid memory read.
2
How do I fix CVE-2017-9114?
To fix CVE-2017-9114, update OpenEXR to any of the following versions: 2.2.1-4.1+deb10u1, 2.2.1-4.1+deb10u2, 2.5.4-2+deb11u1, 3.1.5-5, or 3.1.5-5.1.
3
Which versions of OpenEXR are affected by CVE-2017-9114?
OpenEXR version 2.2.0 is affected by CVE-2017-9114.
4
What happens if CVE-2017-9114 is exploited?
Exploitation of CVE-2017-9114 may lead to application crashes resulting from invalid memory access.
5
Is CVE-2017-9114 a public vulnerability?
Yes, CVE-2017-9114 has been publicly disclosed and is documented in security advisories.