What is the CVSS score of CVE-2016-2292?

CVE-2016-2292 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. EPSS exploitation probability: 1.6%.

Proface Gp Pro Ex Ex Ed CVE-2016-2292

MEDIUM

Out-of-bounds Write (CWE-787)

2016-04-06 ics-cert@hq.dhs.gov

Memory Corruption Buffer Overflow RCE Proface Gp Pro Ex Ex Ed Proface Gp Pro Ex Pfxexedls Proface Gp Pro Ex Pfxexedv Proface Gp Pro Ex Pfxexgrpls

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Apr 06, 2016 - 23:59 cve.org

MEDIUM 6.5

DescriptionCVE.org

AnalysisAI

Stack-based buffer overflow in Pro-face GP-Pro EX EX-ED before 4.05.000, PFXEXEDV before 4.05.000, PFXEXEDLS before 4.05.000, and PFXEXGRPLS before 4.05.000 allows remote attackers to execute. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Write (CWE-787), which allows attackers to write data beyond allocated buffer boundaries leading to code execution or crashes. Stack-based buffer overflow in Pro-face GP-Pro EX EX-ED before 4.05.000, PFXEXEDV before 4.05.000, PFXEXEDLS before 4.05.000, and PFXEXGRPLS before 4.05.000 allows remote attackers to execute arbitrary code via unspecified vectors. Affected products include: Schneider-Electric Proface Gp-Pro Ex Ex-Ed, Schneider-Electric Proface Gp-Pro Ex Pfxexedls, Schneider-Electric Proface Gp-Pro Ex Pfxexedv, Schneider-Electric Proface Gp-Pro Ex Pfxexgrpls. Version information: before 4.05.000.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Validate write boundaries, use memory-safe languages, enable compiler protections (ASLR, stack canaries).