CVE-2017-9629
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stack-based buffer overflow vulnerability exists in Schneider Electric Wonderware ArchestrA Logger versions 2017.426.2307.1 and prior. The flaw may allow a remote attacker to execute arbitrary code in the context of a highly privileged account due to improper bounds checking when processing input on the stack.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2017.426.2307.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Wonderware ArchestrA Logger installationSearch for the ArchestrA Logger program in common installation directories such as C:\Program Files\Wonderware\ArchestrA\Logger or C:\Program Files (x86)\Wonderware\ArchestrA\Logger. Check the Windows Programs and Features control panel for installed software named 'Wonderware ArchestrA Logger' or similar.Affected if The software is not found on the system.
-
Determine installed version numberRight-click the ArchestrA Logger executable or DLL, select Properties, then view the Details tab for the Version information. Alternatively, check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\ArchestrA\Logger for the version value.Affected if The displayed version is 2017.426.2307.1 or lower.
-
Verify ArchestrA Logger service statusOpen Services (services.msc) and locate the Wonderware ArchestrA Logger service. Confirm whether the service is currently running.Affected if The service is running and exposed to network access.
-
Check network listener configurationUse netstat -an to see if the ArchestrA Logger service is listening on any TCP/UDP ports. Review any firewall rules or configuration files that define network binding for the logger service.Affected if The logger service is bound to a network interface and accepting remote connections.
You are affected if Wonderware ArchestrA Logger is installed with version 2017.426.2307.1 or lower and the service is running and network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Wonderware ArchestrA Logger to a patched version beyond 2017.426.2307.1. Until patched, restrict network access to the logger service and apply network segmentation to limit exposure.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-9629 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data