How severe is CVE-2013-6215?

CVE-2013-6215 has a CVSS 2.0 base score of 8.5, rated high severity.

Is CVE-2013-6215 being actively exploited?

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

What products are affected by CVE-2013-6215?

CVE-2013-6215 primarily affects Hp Universal Configuration Management Database. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2013-6215?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2013-6215 published?

CVE-2013-6215 was published on 2014-04-19 and last updated on 2026-06-17.

CVE-2013-6215

CVE-2013-6215 is a high-severity vulnerability in Hp Universal Configuration Management Database with a CVSS 2.0 base score of 8.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 8.5)
EPSS exploit prediction: 3% (83rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Hp Universal Configuration Management Database
Published: 2014-04-19
Last modified: 2026-06-17

Description

Unspecified vulnerability in the Integration Service in HP Universal Configuration Management Database 10.01 and 10.10 allows remote authenticated users to execute arbitrary code via unknown vectors, aka ZDI-CAN-1977.

Frequently asked questions

What is CVE-2013-6215?: Unspecified vulnerability in the Integration Service in HP Universal Configuration Management Database 10.01 and 10.10 allows remote authenticated users to execute arbitrary code via unknown vectors, aka ZDI-CAN-1977.
How severe is CVE-2013-6215?: CVE-2013-6215 has a CVSS 2.0 base score of 8.5, rated high severity.
Is CVE-2013-6215 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (83rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2013-6215?: CVE-2013-6215 primarily affects Hp Universal Configuration Management Database. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2013-6215?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2013-6215 published?: CVE-2013-6215 was published on 2014-04-19 and last updated on 2026-06-17.

References

https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c04219959

Affected products (2)

cpe:2.3:a:hp:universal_configuration_management_database:10.01:*:*:*:*:*:*:*
cpe:2.3:a:hp:universal_configuration_management_database:10.10:*:*:*:*:*:*:*

More vulnerabilities in Hp Universal Configuration Management Database

CVE-2014-2617 — Critical (CVSS 10.0): Unspecified vulnerability in HP Universal CMDB 10.01 and 10.10 allows remote attackers to execute arbitrary code or…
CVE-2014-2616 — High (CVSS 7.5): Unspecified vulnerability in HP Universal CMDB 10.01 and 10.10 allows remote attackers to execute arbitrary code or…
CVE-2014-2615 — High (CVSS 7.5): Unspecified vulnerability in HP Universal CMDB 10.01 and 10.10 allows remote attackers to execute arbitrary code or…
CVE-2014-7883 — Medium (CVSS 5.0): HP Universal CMDB (UCMDB) Probe 9.05, 10.01, and 10.11 enables the HTTP TRACE method, which allows remote attackers to…
CVE-2015-5440 — Medium (CVSS 4.9): HP UCMDB 10.00 and 10.01 before 10.01CUP12, 10.10 and 10.11 before 10.11CUP6, and 10.2x before 10.21 allows local users…
CVE-2013-6214 — Medium (CVSS 4.0): Unspecified vulnerability in the Integration Service in HP Universal Configuration Management Database 9.05, 10.01, and…

All CVEs affecting Hp Universal Configuration Management Database →