CVE-2020-11864

libEMF (aka ECMA-234 Metafile Library) through 1.0.11 allows denial of service (issue 2 of 2).

Published: 2020-05-11 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-11864 is rated Moderate Risk (44/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.44%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-11864

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.27% 0.44% +0.17%
2 2025-11-18 0.44% 0.27% -0.17%
3 2025-10-08 — 0.44% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-11864

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2020-11864

OS Trackers for CVE-2020-11864

vendor priority summary link
debian not yet assigned CVE-2020-11864 not yet assigned priority: Debian including 1 source packages (libemf), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-11864
redhat medium — https://access.redhat.com/security/cve/CVE-2020-11864
suse medium CVE-2020-11864 severity moderate: SUSE including 13 source package names (libEMF-devel-1.0.13-160000.3.2, libEMF-devel-1.0.7-11.3.1, …), 19 product×package rows across 12 product lines (SUSE Linux Enterprise Module for Open Buildservice Development Tools 15 SP3, SUSE Linux Enterprise Server 16.0, … (12 product lines)): Fixed 19. https://www.suse.com/security/cve/CVE-2020-11864/
ubuntu medium CVE-2020-11864 medium priority: Ubuntu including 1 source packages (libemf), 17 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 11, DNE 2, needs-triage 2, ignored 1, released 1. https://ubuntu.com/security/CVE-2020-11864

Affected software / configurations for CVE-2020-11864

Vendor Product Version Raw CPE
libemf_project libemf <= 1.0.11 cpe:2.3:a:libemf_project:libemf:*:*:*:*:*:*:*:*
fedoraproject fedora 31 cpe:2.3:o:fedoraproject:fedora:31:*:*:*:*:*:*:*
opensuse leap 15.1 cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*

References for CVE-2020-11864

cvelogic Threat Intelligence