CVE-2021-31811: Uncontrolled memory consumption in Apache PDFBox

org.apache.pdfbox:pdfbox Updated 02 Oct 2025

Summary

15/06/2021
Yes i
Moderate
5.5

CVE-2021-31811: Uncontrolled memory consumption. Affects org.apache.pdfbox:pdfbox versions >= 2.0.0, < 2.0.24. Fixed in 2.0.24. How to fix ↓

Also tracked for

The same CVE-2021-31811 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

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache PDFBox is an open-source Java library for working with PDF documents. It provides functionality for creating, manipulating, and extracting content from PDF files. The library is widely used in various applications and frameworks that deal with PDF documents. However, versions 2.0.23 and prior of Apache PDFBox are vulnerable to uncontrolled memory consumption.

Vulnerability Detail

The vulnerability in Apache PDFBox arises from a flaw that allows a specially crafted PDF file to trigger an OutOfMemory-Exception during the file loading process. An attacker can exploit this vulnerability by enticing a user to open a malicious PDF file, leading to excessive memory consumption and potentially causing the application to crash or become unresponsive. This vulnerability has a CVSS score of 5.5, indicating a moderate severity level.

How To Fix

Minimum fixed version

2.0.24

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 apply the official fix by upgrading to the latest version of Apache PDFBox.

Conclusion

The uncontrolled memory consumption vulnerability in Apache PDFBox can be mitigated by upgrading to the latest version of the library. It is recommended for developers and users to update their dependencies to ensure they are using a patched version. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for org.apache.pdfbox:pdfbox →

Share this vulnerability

FAQ

Apache PDFBox is a Java library for working with PDF documents. It provides functionality for creating, manipulating, and extracting content from PDF files.

This vulnerability can lead to uncontrolled memory consumption, potentially causing the application to crash or become unresponsive.

An attacker can exploit this vulnerability by enticing a user to open a specially crafted PDF file, triggering excessive memory consumption.

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

No, there is no known workaround. It is crucial to apply the official fix by upgrading to the latest version of Apache PDFBox.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.pdfbox:pdfbox.

How To Fix

Minimum fixed version

2.0.24

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