CVE-2013-1961 json
Stack-based buffer overflow in the t2p_write_pdf_page function in tiff2pdf in libtiff before 4.0.3 allows remote attackers to cause a denia…
published 13y ago modified 4mo ago also EUVD-2013-1951
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.9%
- EPSS 5.9% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in the t2p_write_pdf_page function in tiff2pdf in libtiff before 4.0.3 allows remote attackers to cause a denial of service (application crash) via a crafted image length and resolution in a TIFF image file.
Patch / fix
- tiff Debian 14, Debian 13, Debian 12 4.0.2-6+nmu1
debian advisories DEBIAN-CVE-2013-1961
- tiff Ubuntu 14.04 LTS 4.0.2-4ubuntu3
ubuntu advisories UBUNTU-CVE-2013-1961
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
- libtiff RHEL 6 3.9.4-10.el6_5
- libtiff RHEL 5 3.8.2-19.el5_10
red hat advisories RHSA-2014:0222RHSA-2014:0223
- tiff openSUSE Tumbleweed 4.0.7-1.1
opensuse advisories openSUSE-SU-2024:10554-1
Is CVE-2013-1961 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-1961 updated cvss 4.3
(tiff2pdf): Stack-based buffer overflow with malformed image-length and resolution
-
Red Hat Enterprise Linux (v. 5 server) libtiff 3.8.2-19.el5_10 Red Hat Enterprise Linux Desktop (v. 5 client) libtiff 3.8.2-19.el5_10fixed: vendor fix RHSA-2014:0223
-
Red Hat Enterprise Linux Desktop (v. 6) libtiff 3.9.4-10.el6_5 Red Hat Enterprise Linux Desktop Optional (v. 6) libtiff 3.9.4-10.el6_5fixed: vendor fix RHSA-2014:0222
-
Red Hat Enterprise Linux Desktop Workstation (v. 5 client) libtiff 3.8.2-19.el5_10fixed: vendor fix RHSA-2014:0223
-
Red Hat Enterprise Linux HPC Node (v. 6) libtiff 3.9.4-10.el6_5 Red Hat Enterprise Linux HPC Node Optional (v. 6) libtiff 3.9.4-10.el6_5 Red Hat Enterprise Linux Server (v. 6) libtiff 3.9.4-10.el6_5 Red Hat Enterprise Linux Server Optional (v. 6) libtiff 3.9.4-10.el6_5 Red Hat Enterprise Linux Workstation (v. 6) libtiff 3.9.4-10.el6_5 Red Hat Enterprise Linux Workstation Optional (v. 6) libtiff 3.9.4-10.el6_5fixed: vendor fix RHSA-2014:0222
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
5.91% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
lists.fedoraproject.org
/pipermail/package-announce/2013-May/105253.html
vendor-advisory
-
debian.org
/security/2013/dsa-2698
vendor-advisory
-
lists.opensuse.org
/opensuse-updates/2013-06/msg00080.html
vendor-advisory
-
rhn.redhat.com
/errata/RHSA-2014-0223.html
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2013-May/105828.html
vendor-advisory
-
lists.opensuse.org
/opensuse-updates/2013-06/msg00058.html
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2013-May/104916.html
vendor-advisory
-
secunia.com
/advisories/53237
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/53765
third-party-advisory, vendor-advisory
- bugzilla.redhat.com /show_bug.cgi?id=952131
-
seclists.org
/oss-sec/2013/q2/254
mailing-list
-
securityfocus.com
/bid/59607
vdb-entry
Sources
- CVE List CVE-2013-1961
- NVD CVE-2013-1961
Fencer Intel 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.