Linux ·
Ubuntu · Package update · June 12, 2018
Ubuntu · Package update · June 12, 2018libexiv2-14 0.25-3.1ubuntu0.18.04.1: libexiv2-14 0.25-3.1ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
libexiv2-14 0.25-3.1ubuntu0.18.04.1, released June 12, 2018, fixes 6 CVEs in libexiv2-14. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.
RoutineUnsupported product
CVEs closed
6
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0286
86th percentile
Priority of the 6 CVEs
Patch now 0
Urgent 0
High 0
Routine 6
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| libexiv2-14 | Ubuntu 18.04.6 LTS (bionic) | 0.25-3.1ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2018-11531 | exiv2: Exiv2 0.26 has a heap-based buffer overflow in getData in preview.cpp. | n/a | 0.0286 | None reported |
| Routine | CVE-2018-12264 | exiv2: Exiv2 0.26 has integer overflows in LoaderTiff::getData() in preview.cpp, leading to an out-of-bounds read in Exiv2::... | n/a | 0.0285 | None reported |
| Routine | CVE-2018-12265 | exiv2: Exiv2 0.26 has an integer overflow in the LoaderExifJpeg class in preview.cpp, leading to an out-of-bounds read in Ex... | n/a | 0.0285 | None reported |
| Routine | CVE-2018-10958 | exiv2: In types.cpp in Exiv2 0.26, a large size value may lead to a SIGABRT during an attempt at memory allocation for an Ex... | n/a | 0.0244 | None reported |
| Routine | CVE-2018-10998 | exiv2: An issue was discovered in Exiv2 0.26 | n/a | 0.0241 | None reported |
| Routine | CVE-2018-10999 | exiv2: An issue was discovered in Exiv2 0.26 | n/a | 0.0235 | None reported |
Showing 1 to 6 of 6
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.