dbcve.org
PoiApplication · Apache

CVE-2022-26336

MEDIUM · 5.5 CVSS v3.1 Published 2022-03-04
Fix available
A fix is available. Upgrade to 5.2.1 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A shortcoming in the HMEF package of poi-scratchpad (Apache POI) allows an attacker to cause an Out of Memory exception. This package is used to read TNEF files (Microsoft Outlook and Microsoft Exchange Server). If an application uses poi-scratchpad to parse TNEF files and the application allows untrusted users to supply them, then a carefully crafted file can cause an Out of Memory exception. This issue affects poi-scratchpad version 5.2.0 and prior versions. Users are recommended to upgrade to poi-scratchpad 5.2.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A shortcoming in the HMEF package of Apache POI's poi-scratchpad library allows specially crafted TNEF (Transport Neutral Encapsulation Format) files to trigger an Out of Memory exception. This is a resource exhaustion vulnerability in the TNEF parser that processes files from untrusted sources.

MitigationUpgrade poi-scratchpad to version 5.2.1 or later. Additionally, consider implementing file size limits and memory constraints when processing untrusted TNEF files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PoiApplication
Affected:< 5.2.1
Active Iq Unified ManagerApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate poi-scratchpad library
    Search for poi-scratchpad JAR files in your application dependencies, build files (Maven pom.xml, Gradle build.gradle), or lib directories. Look for files named poi-scratchpad-*.jar
    Affected if poi-scratchpad library is present in your environment
  2. Identify poi-scratchpad version
    Check the version number in the JAR filename or in your dependency management file (Maven: mvn dependency:list, Gradle: ./gradlew dependencies, or inspect the MANIFEST.MF inside the JAR)
    Affected if Version is lower than 5.2.1 (for example, 5.2.0, 5.1.0, 4.x.x, etc.)
  3. Determine if HMEF/TNEF processing is used
    Search codebase for imports of HMEF classes: org.apache.poi.hmef.* or usage of TNEFAttachment/Attendee classes. Check if your application processes email attachments or calendar files that may contain TNEF content
    Affected if Code imports or uses HMEF/TNEF classes from poi-scratchpad to process files from untrusted sources
  4. Check for NetApp Active IQ Unified Manager
    If you run NetApp Active IQ Unified Manager, verify the product version via the web UI (Help > About) or command line (um version)
    Affected if Any version of NetApp Active IQ Unified Manager is running, as all versions are affected

You are affected if poi-scratchpad version is below 5.2.1 AND your application uses the HMEF module to process untrusted TNEF files, or if you run any version of NetApp Active IQ Unified Manager.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.2.1 or later
Fixed in 5.2.1
Interim mitigation

Upgrade poi-scratchpad to version 5.2.1 or later. Additionally, consider implementing file size limits and memory constraints when processing untrusted TNEF files.

Recommended fix High confidence

poi-scratchpad 5.2.1

  1. Identify the build system used in your project (Maven, Gradle, or manual JAR management)
  2. If using Maven, update the poi-scratchpad dependency version to 5.2.1 in pom.xml: change <version> to 5.2.1
  3. Run mvn clean compile or mvn clean package to fetch and integrate the updated dependency
  4. If using Gradle, update the poi-scratchpad dependency to version 5.2.1 in build.gradle
  5. If using manual JAR management, download poi-scratchpad-5.2.1.jar and its required dependencies from the Apache POI website
  6. Replace the old poi-scratchpad JAR files in your application's classpath with the new version 5.2.1
  7. Rebuild and redeploy the application
  8. Verify the application functions correctly with the new library version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Poi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26336 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data