CVE-2020-25198
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 · uneditedThe built-in WEB server for MOXA NPort IAW5000A-I/O firmware version 2.1 or lower has incorrectly implemented protections from session fixation, which may allow an attacker to gain access to a session and hijack it by stealing the user’s cookies.
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 confidenceThe MOXA NPort IAW5000A-I/O device's built-in web server (firmware v2.1 and below) has session fixation protections that are incorrectly implemented, allowing attackers to steal user session cookies and hijack sessions. This stems from the session ID not being properly regenerated upon authentication, leaving it vulnerable to fixation attacks.
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<= 2.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm device modelIdentify the exact model of the Moxa device. The vulnerability affects specifically the NPort IAW5000A-I/O series. Check the device label, web interface, or management console to verify the model number matches this variant.Affected if Device is not a NPort IAW5000A-I/O model
-
Check firmware versionAccess the device's web interface or management console and locate the firmware version information, typically found under System Settings, Status, or About pages. Compare the installed version against the affected range of <= 2.1.Affected if Firmware version is 2.1 or lower
-
Verify web server is enabledCheck the device configuration to confirm the built-in web server (HTTP/HTTPS) is enabled. This is usually found under Network Settings, Services, or Port Configuration. The vulnerability exists in the web server component.Affected if Web server is enabled and accessible
-
Inspect session cookie behaviorIf possible, capture a session cookie before and after logging into the web interface. Compare the session ID values - in a vulnerable device, the session ID remains unchanged after authentication (session fixation). Alternatively, review any available session management configuration.Affected if Session ID does not change after successful authentication (remains the same as pre-login value)
Device is affected if it is a NPort IAW5000A-I/O with firmware version 2.1 or below and the built-in web server is enabled, allowing session fixation attacks.
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 dataUpgrade firmware to a version higher than 2.1 that implements proper session ID regeneration on login and secure session cookie attributes (HttpOnly, Secure, SameSite). If no update is available, consider network segmentation to limit web server exposure.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25198 — 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-2020-25198 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