Skip to content
Fencer Vulns
critical 9.8

CVE-2017-9629 json

A Stack-Based Buffer Overflow issue was discovered in Schneider Electric Wonderware ArchestrA Logger, versions 2017.426.2307.1 and prior.

published 2017-07-07 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18560

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.8%
EPSS 9.8% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

A Stack-Based Buffer Overflow issue was discovered in Schneider Electric Wonderware ArchestrA Logger, versions 2017.426.2307.1 and prior. The stack-based buffer overflow vulnerability has been identified, which may allow a remote attacker to execute arbitrary code in the context of a highly privileged account.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-17-187-04 updated cvss 9.8

Schneider Electric Wonderware ArchestrA Logger

  • Schneider Electric Software, LLC Wonderware ArchestrA Logger <= 2017.426.2307.1
    affected: vendor fix, mitigation “For more information about this vulnerability and patch, please refer to Schneider Electric Security Bulletin LFSec00000116, which is available at the following location:” gcsresource.invensys.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

9.79% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • n/a Schneider Electric Wonderware ArchestrA Logger

Classification

Weakness
  • CWE-121 Stack-based Buffer Overflow
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.