How severe is CVE-2010-5203?

CVE-2010-5203 has a CVSS 2.0 base score of 6.9, rated medium severity.

Is CVE-2010-5203 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2010-5203?

CVE-2010-5203 primarily affects Ncp-e Secure Client. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2010-5203?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2010-5203 published?

CVE-2010-5203 was published on 2012-09-06 and last updated on 2026-06-16.

CVE-2010-5203

CVE-2010-5203 is a medium-severity vulnerability in Ncp-e Secure Client with a CVSS 2.0 base score of 6.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 6.9)
EPSS exploit prediction: 0% (27th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Ncp-e Secure Client
Published: 2012-09-06
Last modified: 2026-06-16

Description

Multiple untrusted search path vulnerabilities in NCP Secure Enterprise Client before 9.21 Build 68, Secure Entry Client before 9.23 Build 18, and Secure Client - Juniper Edition before 9.23 Build 18 allow local users to gain privileges via a Trojan horse (1) dvccsabase002.dll, (2) conman.dll, (3) kmpapi32.dll, or (4) ncpmon2.dll file in the current working directory, as demonstrated by a directory that contains a .pcf or .spd file. NOTE: some of these details are obtained from third party information.

Frequently asked questions

What is CVE-2010-5203?: Multiple untrusted search path vulnerabilities in NCP Secure Enterprise Client before 9.21 Build 68, Secure Entry Client before 9.23 Build 18, and Secure Client - Juniper Edition before 9.23 Build 18 allow local users to gain privileges via a Trojan horse (1) dvccsabase002.dll, (2) conman.dll, (3) kmpapi32.dll, or (4) ncpmon2.dll file in the current working directory, as demonstrated by a directory that contains a .pcf or .spd file. NOTE: some of these details are obtained from third party information.
How severe is CVE-2010-5203?: CVE-2010-5203 has a CVSS 2.0 base score of 6.9, rated medium severity.
Is CVE-2010-5203 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-5203?: CVE-2010-5203 primarily affects Ncp-e Secure Client. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-5203?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2010-5203 published?: CVE-2010-5203 was published on 2012-09-06 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:ncp-e:secure_client:*:*:juniper:*:*:*:*:*
cpe:2.3:a:ncp-e:secure_enterprise_client:*:*:*:*:*:*:*:*
cpe:2.3:a:ncp-e:secure_entry_client:*:*:*:*:*:*:*:*