CVE-2016-9678 : Use-after-free vulnerability in Citrix Provisioning Services before 7.12 allows

Use-after-free vulnerability in Citrix Provisioning Services before 7.12 allows attackers to execute arbitrary code via unspecified vectors.

Published 2017-01-18 22:59:01

Updated 2017-01-23 19:50:45

Source MITRE

View at NVD, CVE.org

Vulnerability category: Memory CorruptionExecute code

Products affected by CVE-2016-9678

Citrix » Provisioning Services » Version: 7.7
cpe:2.3:a:citrix:provisioning_services:7.7:*:*:*:*:*:*:*
Matching versions
Citrix » Provisioning Services » Version: 7.8
cpe:2.3:a:citrix:provisioning_services:7.8:*:*:*:*:*:*:*
Matching versions
Citrix » Provisioning Services » Version: 7.9
cpe:2.3:a:citrix:provisioning_services:7.9:*:*:*:*:*:*:*
Matching versions
Citrix » Provisioning Services » Version: 7.1
cpe:2.3:a:citrix:provisioning_services:7.1:*:*:*:*:*:*:*
Matching versions
Citrix » Provisioning Services » Version: 7.0
cpe:2.3:a:citrix:provisioning_services:7.0:*:*:*:*:*:*:*
Matching versions
Citrix » Provisioning Services » Version: 7.6
cpe:2.3:a:citrix:provisioning_services:7.6:*:*:*:*:*:*:*
Matching versions
Citrix » Provisioning Services » Version: 7.11
cpe:2.3:a:citrix:provisioning_services:7.11:*:*:*:*:*:*:*
Matching versions

EPSS FAQ

3.45%

Probability of exploitation activity in the next 30 days EPSS Score History

~ 86 %

Percentile, the proportion of vulnerabilities that are scored at or less

Base Score	Base Severity	CVSS Vector	Exploitability Score	Impact Score	Score Source
7.5	HIGH	AV:N/AC:L/Au:N/C:P/I:P/A:P	10.0	6.4	NIST
Access Vector: Network Access Complexity: Low Authentication: None Confidentiality Impact: Partial Integrity Impact: Partial Availability Impact: Partial
9.8	CRITICAL	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H	3.9	5.9	NIST
Attack Vector: Network Attack Complexity: Low Privileges Required: None User Interaction: None Scope: Unchanged Confidentiality: High Integrity: High Availability: High

CWE-416 Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Assigned by: nvd@nist.gov (Primary)

Jump to