CVE-2018-0202
Description revised (poc_count, poc_public, poc_url). The record changed; nothing in the observed threat did.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- No fix version is held. The CNA's first reference is the place to look: usn.ubuntu.com
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
clamscan in ClamAV before 0.99.4 contains a vulnerability that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to improper input validation checking mechanisms when handling Portable Document Format (.pdf) files sent to an affected device. An unauthenticated, remote attacker could exploit this vulnerability by sending a crafted .pdf file to an affected device. This action could cause an out-of-bounds read when ClamAV scans the malicious file, allowing the attacker to cause a DoS condition. This concerns pdf_parse_array and pdf_parse_string in libclamav/pdfng.c. Cisco Bug IDs: CSCvh91380, CSCvh91400.
- weakness
- out-of-bounds read
- affected
- n/a ClamAV
- published ranges
- clamav <= 0.99.3; canonical ubuntu linux 12.04; canonical ubuntu linux 14.04; canonical ubuntu linux 16.04; and 2 more on the CVE page
- fixed in
- No fix version in held sources.
- assigned by
- cisco
- published
- 2018-03-27
check us usn.ubuntu.com bugzilla.clamav.net bugzilla.clamav.net lists.debian.org
Exploit code held, dated
- exploit code
- 1 public proof-of-concept repository, first seen 2018-11-24 (PoC-in-GitHub).
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 14 Apr 2021 | 0.02262 | |
| 4 Feb 2022 | 0.01319 | |
| 7 Mar 2023 | 0.00334 | scoring model v2023.03.01 |
| 21 Mar 2023 | 0.00465 | |
| 17 Mar 2025 | 0.03034 | scoring model v2025.03.14 |
| 19 Mar 2025 | 0.129 | crossed 0.10 |
| 20 Mar 2025 | 0.03034 | crossed 0.10 |
| 27 Mar 2025 | 0.129 | crossed 0.10 |
| 28 Mar 2025 | 0.03034 | crossed 0.10 |
| 29 Mar 2025 | 0.129 | crossed 0.10 |
| 30 Mar 2025 | 0.03034 | crossed 0.10 |
| 15 Jun 2026 | 0.02672 | scoring model v2026.06.15 |
| 23 Aug 2026 | 0.05153 | |
| 30 Aug 2026 | 0.0263 | |
| 5 Sep 2026 | 0.05119 | |
| 6 Sep 2026 | 0.02581 |
36 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.03 on 2026-09-06 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- No fix version is held. One published by the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2018-0202', '2026-11-01T23:59:59.999999Z', now());