CVE-2021-3630 json
An out-of-bounds write vulnerability was found in DjVuLibre in DJVU::DjVuTXT::decode() in DjVuText.cpp via a crafted djvu file which may le…
published 2021-06-30 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-26932
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
An out-of-bounds write vulnerability was found in DjVuLibre in DJVU::DjVuTXT::decode() in DjVuText.cpp via a crafted djvu file which may lead to crash and segmentation fault. This flaw affects DjVuLibre versions prior to 3.5.28.
Patch / fix
- djvulibre_project djvulibre 3.5.28
- djvulibre Debian 14, Debian 13, Debian 12 3.5.27.1-12
debian advisories DEBIAN-CVE-2021-3630
- djvulibre Ubuntu 18.04 LTS 3.5.27.1-8ubuntu0.4
- djvulibre Ubuntu Pro 16.04 LTS 3.5.27.1-5ubuntu0.1+esm2
ubuntu advisories UBUNTU-CVE-2021-3630
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- djvulibre SLES for SAP 15 SP1, SLES for SAP 15, SLES 15-LTSS +10 more 3.5.27-3.19.1
- djvulibre SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES for SAP 12 SP3 +11 more 3.5.25.3-5.19.2
- djvulibre SLE Module for Package Hub 15 SP3, SLE Module for Package Hub 15 SP2, SLE Module for Desktop Applications 15 SP3 +1 more 3.5.27-11.11.1
- djvulibre SLES 11 SP4-LTSS, SLE Point of Sale 11 SP3 3.5.21-3.18.1
- djvulibre SLES 11 SP4-LTSS, SLE Point of Sale 11 SP3 3.5.21-3.15.1
suse advisories SUSE-SU-2021:2796-1SUSE-SU-2021:2621-1SUSE-SU-2021:2619-1SUSE-SU-2021:14773-1SUSE-SU-2021:14761-1
- djvulibre openSUSE Leap 15.2 3.5.27-lp152.7.9.1
- djvulibre openSUSE Leap 15.3 3.5.27-11.11.1
opensuse advisories openSUSE-SU-2021:1112-1openSUSE-SU-2021:2619-1
- djvulibre Alpine 3.24, Alpine 3.23, Alpine 3.22 +7 more 3.5.28-r1
alpine advisories ALPINE-CVE-2021-3630
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2021-3630 updated cvss 5.5
djvulibre: out-of-bounds write in DJVU::DjVuTXT::decode() in DjVuText.cpp
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Affected products
- n/a djvulibre
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
bugzilla.redhat.com
/show_bug.cgi?id=1977427
issue-tracking, patch, third-party-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/XVKYWV4P5XGA3FXKGFB443MKC32L7YQB/
vendor-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/Q3B4QZCICPZRDXA2HOIACSQNZB2VEHSM/
vendor-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/CIZIAJWGKI26DKDOGJS7J7CIQGHHMIHG/
vendor-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/7MRXCW4BUGAJLGF6IWQWUZ2YBICMZCPK/
vendor-advisory
-
debian.org
/security/2021/dsa-5032
vendor-advisory, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2021/07/msg00002.html
mailing-list, third-party-advisory
Sources
- CVE List CVE-2021-3630
- NVD CVE-2021-3630
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.