CVE-2017-9631
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 Null Pointer Dereference issue was discovered in Schneider Electric Wonderware ArchestrA Logger, versions 2017.426.2307.1 and prior. The null pointer dereference vulnerability could allow an attacker to crash the logger process, causing a denial of service for logging and log-viewing (applications that use the Wonderware ArchestrA Logger continue to run when the Wonderware ArchestrA Logger service is unavailable).
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 · moderate confidenceA null pointer dereference vulnerability in Schneider Electric Wonderware ArchestrA Logger (versions 2017.426.2307.1 and prior) allows an attacker to crash the logger process by triggering the dereference of an uninitialized or null pointer, resulting in denial of service for logging and log-viewing functions.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the Wonderware ArchestrA Logger installationSearch for ArchestrA Logger executable (typically named ArchestrA Logger.exe or similar) or check Windows Programs and Features for Wonderware ArchestrA Logger entry. Note the installation directory.Affected if The software is installed on the system.
-
Determine the installed version numberRight-click the ArchestrA Logger executable, select Properties, and view the Version tab to obtain the File Version. Alternatively, check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\ArchestrA\Logger (or similar path) for a Version or ProductVersion entry.Affected if The version displayed is 2017.426.2307.1 or lower.
-
Verify the logger service is runningOpen Windows Services (services.msc), locate the ArchestrA Logger service, and check its Status. Or run 'sc query ArchestrALogger' from command prompt.Affected if The service is running and accepting requests, making it susceptible to the null pointer dereference crash.
-
Assess network exposure of the logger serviceRun 'netstat -an | findstr [port]' where the logger port is typically 1234 or 5450 (common Wonderware ports), or review firewall rules for inbound access to ArchestrA Logger ports from untrusted networks.Affected if The logger port is open to untrusted or external network segments, allowing remote attackers to trigger the crash.
You are affected if Wonderware ArchestrA Logger version 2017.426.2307.1 or prior is installed and the logger service is running and accessible to potential attackers.
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 version beyond 2017.426.2307.1 that includes the patch for this vulnerability. If no patched version is available, implement network segmentation and access controls to limit exposure to untrusted users.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9631 — 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-9631 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