CVE-2013-3718

MEDIUMNVD 5.55.5—

5.5

evince is missing a check on number of pages which can lead to a segmentation fault

CVSS v3: 5.5
EG Score: 5.5(medium)
EPSS: 67.1%
KEV: Not listed

Published

November 1, 2019

Last Modified

November 21, 2024

References (8)

cve@mitrehttp://bugzilla.gnome.org/show_bug.cgi?id=701302
cve@mitrehttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-3718
cve@mitrehttps://bugzilla.suse.com/show_bug.cgi?id=CVE-2013-3718
cve@mitrehttps://security-tracker.debian.org/tracker/CVE-2013-3718
af854a3a-2127-422b-91ae-364da2661108http://bugzilla.gnome.org/show_bug.cgi?id=701302
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-3718
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.suse.com/show_bug.cgi?id=CVE-2013-3718
af854a3a-2127-422b-91ae-364da2661108https://security-tracker.debian.org/tracker/CVE-2013-3718

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-20Improper Input Validation

Data Freshness Timeline

(refreshed 12× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-06 13:45 UTCepss_batch
2026-06-06 13:45 UTCepss_batch
2026-06-05 22:44 UTCepss_batch
2026-06-05 22:44 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch

Frequently asked(5)

What is CVE-2013-3718?

CVE-2013-3718 is a medium vulnerability published on November 1, 2019. evince is missing a check on number of pages which can lead to a segmentation fault

When was CVE-2013-3718 disclosed?

CVE-2013-3718 was first published in the National Vulnerability Database on November 1, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2013-3718 actively exploited?

CVE-2013-3718 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 67.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2013-3718?

CVE-2013-3718 has a CVSS v3 base score of 5.5 (NVD).

How do I remediate CVE-2013-3718?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-3718, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-3718

Explore →

Is Your Infrastructure Affected by CVE-2013-3718?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2013-3718

📅 Published

🔄 Last Modified

🔗 References (8)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2013-3718?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (8)

Frequently asked(5)

Related CVEs(same CWE)