CVE-2022-24613: Improper Handling of Exceptional Conditions in metadata-extractor

Summary

25/02/2022
Yes i
Moderate
5.5

CVE-2022-24613: Improper Handling of Exceptional Conditions inn metadata-extractor. Affects com.drewnoakes:metadata-extractor versions < 2.18.0. Fixed in 2.18.0. How to fix ↓

Also tracked for

The same CVE-2022-24613 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The metadata-extractor is a Maven package that is used for extracting metadata from various file formats, including JPEG files. It provides functionality to parse and extract metadata information such as camera details, GPS coordinates, and timestamps from these files. However, versions up to 2.16.0 of metadata-extractor are vulnerable to an improper handling of exceptional conditions, which can lead to uncaught exceptions and application crashes when parsing specially crafted JPEG files. This vulnerability can be exploited to launch denial of service attacks against services that utilize the metadata-extractor library.

Vulnerability Detail

The vulnerability in metadata-extractor arises from its inability to handle exceptional conditions properly while parsing certain JPEG files. This can result in the generation of uncaught exceptions, leading to application crashes. An attacker can exploit this vulnerability by providing a specially crafted JPEG file to a vulnerable application, causing it to crash. This can be used as a means to disrupt the availability of services that rely on the metadata-extractor library. The vulnerability has a CVSS score of 5.5, indicating a moderate severity level.

How To Fix

Minimum fixed version

2.18.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of the metadata-extractor library to mitigate the risk.

Conclusion

The metadata-extractor library up to version 2.16.0 is vulnerable to improper handling of exceptional conditions while parsing JPEG files. This can result in application crashes and can be exploited for denial of service attacks. To mitigate the risk, it is crucial to upgrade to version 2.18.0 or later of the library. For further assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for com.drewnoakes:metadata-extractor →

Share this vulnerability

FAQ

metadata-extractor is a Maven package used for extracting metadata from various file formats, including JPEG files. It provides functionality to parse and extract metadata information such as camera details, GPS coordinates, and timestamps from these files.

The vulnerability in metadata-extractor can lead to application crashes when parsing specially crafted JPEG files. This can be exploited to launch denial of service attacks against services that use the metadata-extractor library.

To fix this vulnerability, it is recommended to upgrade to version 2.18.0 or later of the metadata-extractor library. This version includes the necessary fixes to handle exceptional conditions properly while parsing JPEG files.

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of the metadata-extractor library to mitigate the risk.

The vulnerability has a CVSS score of 5.5, indicating a moderate severity level.

Related vulnerabilities

Recent vulnerabilities recorded for com.drewnoakes:metadata-extractor.

How To Fix

Minimum fixed version

2.18.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback