CVE-2018-16554

CVE-2018-16554 is a high-severity vulnerability in Jhead Project Jhead with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-134.

Key facts

Description

The ProcessGpsInfo function of the gpsinfo.c file of jhead 3.00 may allow a remote attacker to cause a denial-of-service attack or unspecified other impact via a malicious JPEG file, because of inconsistency between float and double in a sprintf format string during TAG_GPS_ALT handling.

Frequently asked questions

What is CVE-2018-16554?
The ProcessGpsInfo function of the gpsinfo.c file of jhead 3.00 may allow a remote attacker to cause a denial-of-service attack or unspecified other impact via a malicious JPEG file, because of inconsistency between float and double in a sprintf format string during TAG_GPS_ALT handling.
How severe is CVE-2018-16554?
CVE-2018-16554 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-16554 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-16554?
CVE-2018-16554 affects Jhead Project Jhead. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-16554?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-16554 published?
CVE-2018-16554 was published on 2018-09-16 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Jhead Project Jhead

All CVEs affecting Jhead Project Jhead →

Other CWE-134 vulnerabilities

Browse all CWE-134 vulnerabilities →