CVE-2017-13702
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 · uneditedAn issue was discovered on MOXA EDS-G512E 5.1 build 16072215 devices. Cookies can be stolen, manipulated, and reused.
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 confidenceThe MOXA EDS-G512E industrial Ethernet switch firmware 5.1 build 16072215 contains a session management vulnerability where cookies can be stolen, manipulated, and reused, indicating missing or insufficient cookie protection mechanisms such as secure flags, HttpOnly directives, or proper session token validation.
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= 5.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Confirm device model is Moxa EDS-G512ELog into the device web interface and navigate to System Settings or System Information to verify the model name displays as EDS-G512EAffected if The device model is Moxa EDS-G512E and firmware version displays as 5.1 or build 16072215
-
Check firmware versionIn the device web interface, locate the firmware version information typically found under System > Information or a System Settings page. Record the exact firmware version and build number displayedAffected if Firmware version shows exactly 5.1 or build number 16072215
-
Inspect cookie Set-Cookie headersUse a browser developer tool or proxy (such as Burp Suite or Fiddler) to capture HTTP responses from the device login page and after authentication. Examine any Set-Cookie headers in the responsesAffected if Set-Cookie headers for session cookies lack the 'Secure' flag, indicating cookies can be transmitted over non-HTTPS connections
-
Check for HttpOnly flag on session cookiesIn the captured HTTP headers from step 3, examine the Set-Cookie headers for the presence of the 'HttpOnly' directiveAffected if Session cookies do not include the HttpOnly attribute, making them accessible to JavaScript and vulnerable to theft via XSS
-
Verify session cookie behaviorLog out and back into the device web interface. Capture new session cookies and compare them to previous session cookies to see if old cookies remain valid after re-authenticationAffected if Old session cookies can be reused after logging out and logging back in, indicating insufficient session token validation
A user is affected if they have a Moxa EDS-G512E device running firmware version 5.1 (build 16072215) and the device's web session cookies lack Secure and HttpOnly flags or allow session reuse.
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 dataContact MOXA for the latest firmware patch addressing this cookie vulnerability; as a compensating control, restrict network access to the device management interface via VLAN segmentation or firewall rules.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13702 — 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-13702 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