Skip to content
This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page. View CVE-2021-37819 →
Unrated

Vulnerability in libitext-java

DEBIAN-CVE-2021-37819 First seen on SecPulse

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as DEBIAN-CVE-2021-37819 has been found in libitext-java.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libitext-java to 2.1.7-16 or later.
If unsure, ask your IT team or search "libitext-java DEBIAN-CVE-2021-37819" on the vendor's site.

DEBIAN-CVE-2021-37819 (libitext-java)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.1.7-16 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

What is the problem

A vulnerability (unclassified) exists in libitext-java.

Affected scope

Check the vendor advisory for the affected versions of libitext-java.

Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

How to fix

Update to 2.1.7-16.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libitext-java' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposureidentify
    grep -r 'libitext-java' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で libitext-java を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patchpatch
    Upgrade libitext-java to 2.1.7-16

    ステージング環境で 2.1.7-16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Debian:12 libitext-java
All versions
—
Debian:13 libitext-java
< 2.1.7-16
2.1.7-16
Debian:14 libitext-java
< 2.1.7-16
2.1.7-16
Debian:12 libitext1-java
All versions
—
Debian:12 libitext5-java
All versions
—
Debian:13 libitext5-java
< 5.5.13.3-4
5.5.13.3-4
Debian:14 libitext5-java
< 5.5.13.3-4
5.5.13.3-4
Debian:12 pdftk
< 2.02-5
2.02-5
Debian:12 pdftk-java
< 3.3.2-1
3.3.2-1
Debian:13 pdftk-java
< 3.3.2-1
3.3.2-1
Debian:14 pdftk-java
< 3.3.2-1
3.3.2-1
Original description The description as published by the source.

PDF Labs pdftk-java v3.2.3 was discovered to contain an infinite loop via the component /text/pdf/PdfReader.java.

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details