CVE-2013-4978 json
Stack-based buffer overflow in AloahaPDFViewer 5.0.0.7 and earlier in Aloaha PDF Suite FREE allows remote attackers to execute arbitrary co…
published 12y ago modified 4mo ago also EUVD-2013-4822
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.6%
- EPSS 6.6% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
Stack-based buffer overflow in AloahaPDFViewer 5.0.0.7 and earlier in Aloaha PDF Suite FREE allows remote attackers to execute arbitrary code via a crafted PDF file.
Is CVE-2013-4978 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 FencerTimeline
- First public exploit (EDB-38742)
- Published
Exploit prediction
6.58% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-38742 Aloaha PDF Suite - Remote Stack Buffer Overflow remote, 2013-08-28
- coresecurity.com http://www.coresecurity.com/advisories/aloaha-pdf-suite-buffer-overflow-vulnerability referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/bugtraq/2013-08/0179.html referenced PoC, tagged "exploit" by a source, unverified
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
-
coresecurity.com
/advisories/aloaha-pdf-suite-buffer-overflow-vulnerability
exploit
-
archives.neohapsis.com
/archives/bugtraq/2013-08/0179.html
mailing-list, exploit
-
secunia.com
/advisories/54585
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/62036
vdb-entry
Sources
- CVE List CVE-2013-4978
- NVD CVE-2013-4978
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.