Skip to content

← Public intelligence

Maven package

com.drewnoakes:metadata-extractor

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.5MavenPublished

    Improper Handling of Exceptional Conditions inn metadata-extractor

    CVE-2022-24613 · GHSA-p5pg-wm9q-8v6r

    Affected
    • Maven com.drewnoakes:metadata-extractor < 2.18.0
    Fixed in
    2.18.0· Vendor fix available
    Issue
    metadata-extractor up to 2.16.0 can throw various uncaught exceptions while parsing a specially crafted JPEG file, which could result in an application crash. This could be used to mount a denial of service attack against services that use metadata-extractor library.

    Recommended action: Upgrade to 2.18.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.1MavenPublished

    Allocation of Resources Without Limits or Throttling in metadata-extractor

    CVE-2022-24614 · GHSA-4v6p-cxf9-98rf

    Affected
    • Maven com.drewnoakes:metadata-extractor < 2.18.0
    Fixed in
    2.18.0· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 2.18.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →