Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Allocation of Resources Without Limits or Throttling in metadata-extractorGHSA-4v6p-cxf9-98rf

MEDIUMFix: drewnoakes/metadata-extractor#570

GHSA-4v6p-cxf9-98rf is a medium-severity (CVSS 5.5) CWE-770 vulnerability in com.drewnoakes:metadata-extractor. A fix is available for com.drewnoakes:metadata-extractor — see the affected versions and patch details below.

Also known asCVE-2022-24614
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.00%0.41%0.82%1.23%0.3%0.3%0.7%0.7%0.7%Apr 26Jul 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-4v6p-cxf9-98rf by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
☕com.drewnoakes:metadata-extractor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

When reading a specially crafted JPEG file, metadata-extractor up to 2.16.0 can be made to allocate large amounts of memory that finally leads to an out-of-memory error even for very small inputs. This could be used to mount a denial of service attack against services that use metadata-extractor library.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.drewnoakes:metadata-extractorall versions2.18.0com.drewnoakes:metadata-extractor:2.18.0

Affected Products

1 product · 1 configurations
Application
metadata-extractormetadata-extractor_project
< 2.18.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.drewnoakes:metadata-extractor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.drewnoakes:metadata-extractor to 2.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4v6p-cxf9-98rf is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow
ProductFixed inAdvisory
Red Hat Fuse 7.11metadata-extractorRHSA-2022:5532

Frequently Asked Questions

When reading a specially crafted JPEG file, metadata-extractor up to 2.16.0 can be made to allocate large amounts of memory that finally leads to an out-of-memory error even for very small inputs. This could be used to mount a denial of service attack against services that use metadata-extractor library.
O3 Security · Impact-Aware SCA

Is GHSA-4v6p-cxf9-98rf in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Allocation of Resources Without Limits or Throttling in…