Vulnerability Details CVE-2019-17179
4.1.0, 4.1.1, 4.1.2, 4.1.2.3, 4.1.2.6, 4.1.2.7, 4.2.0, 4.2.1, 4.2.2, 5.0.0, 5.0.0.5, 5.0.0.6, 5.0.1, 5.0.1.1, 5.0.1.2, 5.0.1.3, 5.0.1.4, 5.0.1.5, 5.0.1.6, 5.0.1.7, 5.0.2, fixed in version 5.0.2.1
Exploit prediction scoring system (EPSS) score
EPSS Score 0.015
EPSS Ranking 80.8%
CVSS Severity
CVSS v3 Score 6.1
CVSS v2 Score 4.3
Products affected by CVE-2019-17179
-
cpe:2.3:a:open-emr:openemr:-
-
cpe:2.3:a:open-emr:openemr:2.0.1.2
-
cpe:2.3:a:open-emr:openemr:2.7
-
cpe:2.3:a:open-emr:openemr:2.7.1
-
cpe:2.3:a:open-emr:openemr:2.7.2
-
cpe:2.3:a:open-emr:openemr:2.7.3
-
cpe:2.3:a:open-emr:openemr:2.8.0
-
cpe:2.3:a:open-emr:openemr:2.8.1
-
cpe:2.3:a:open-emr:openemr:2.8.2
-
cpe:2.3:a:open-emr:openemr:2.8.3
-
cpe:2.3:a:open-emr:openemr:2.9.0
-
cpe:2.3:a:open-emr:openemr:3.0.0
-
cpe:2.3:a:open-emr:openemr:3.0.1
-
cpe:2.3:a:open-emr:openemr:3.1.0
-
cpe:2.3:a:open-emr:openemr:3.2.0
-
cpe:2.3:a:open-emr:openemr:4.0.0
-
cpe:2.3:a:open-emr:openemr:4.1.0
-
cpe:2.3:a:open-emr:openemr:4.1.1
-
cpe:2.3:a:open-emr:openemr:4.1.2
-
cpe:2.3:a:open-emr:openemr:4.1.2.3
-
cpe:2.3:a:open-emr:openemr:4.1.2.6
-
cpe:2.3:a:open-emr:openemr:4.1.2.7
-
cpe:2.3:a:open-emr:openemr:4.2.0
-
cpe:2.3:a:open-emr:openemr:4.2.0.3
-
cpe:2.3:a:open-emr:openemr:4.2.1
-
cpe:2.3:a:open-emr:openemr:4.2.2
-
cpe:2.3:a:open-emr:openemr:5.0.0
-
cpe:2.3:a:open-emr:openemr:5.0.0.5
-
cpe:2.3:a:open-emr:openemr:5.0.0.6
-
cpe:2.3:a:open-emr:openemr:5.0.1
-
cpe:2.3:a:open-emr:openemr:5.0.1-6
-
cpe:2.3:a:open-emr:openemr:5.0.1.1
-
cpe:2.3:a:open-emr:openemr:5.0.1.2
-
cpe:2.3:a:open-emr:openemr:5.0.1.3
-
cpe:2.3:a:open-emr:openemr:5.0.1.4
-
cpe:2.3:a:open-emr:openemr:5.0.1.5
-
cpe:2.3:a:open-emr:openemr:5.0.1.6
-
cpe:2.3:a:open-emr:openemr:5.0.1.7
-
cpe:2.3:a:open-emr:openemr:5.0.2