CVE-2018-9080
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 · uneditedFor some Iomega, Lenovo, LenovoEMC NAS devices versions 4.1.402.34662 and earlier, by setting the Iomega cookie to a known value before logging into the NAS's web application, the NAS will not provide the user a new cookie value. This allows an attacker who knows the cookie's value to compromise the user's session.
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 confidenceThis is a session fixation vulnerability in NAS web applications where the Iomega cookie value set before authentication is not replaced with a new secure value after login. An attacker can pre-set a known cookie value and then hijack the user's session once they authenticate, as the same cookie value remains active.
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= 4.1.402.34662= 4.1.402.34662= 4.1.402.34662= 4.1.402.34662= 4.1.402.34662= 4.1.402.34662= 4.1.402.34662= 4.1.402.34662CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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.
-
Identify firmware versionAccess the NAS web interface and check System > Settings > About, or use the CLI command 'version' or 'system show version' to retrieve the installed firmware versionAffected if The installed firmware version is exactly 4.1.402.34662 (any of the listed models: Px12 450r, Px12 400r, Px4 300r, Px6 300d, Px4 300d, Px2 300d, Ix4 300d, Ix2)
-
Access the NAS web login pageNavigate to the NAS management web interface using its IP address and observe the HTTP response headers and cookiesAffected if The web interface is accessible and returns a Set-Cookie header containing an 'Iomega' cookie value before any authentication occurs
-
Verify session cookie behaviorUsing a browser or HTTP tool, capture the Iomega cookie value presented by the login page. Then authenticate with valid credentials. After login, inspect the Iomega cookie value againAffected if The Iomega cookie value remains identical before and after authentication (the cookie is not regenerated on login)
-
Check network accessibilityDetermine if the NAS web management interface is exposed to untrusted networks by reviewing firewall rules or network ACLs restricting access to port 443/80Affected if The NAS web interface is accessible from untrusted network segments (the vulnerability requires an attacker to be able to set a cookie value before the victim authenticates)
You are affected if your NAS runs firmware version 4.1.402.34662 and the Iomega session cookie is not regenerated after authentication, making session fixation possible for attackers who can reach the login page.
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 NAS firmware to a version newer than 4.1.402.34662 to receive the vendor patch. As an interim control, restrict network access to the NAS management interface to trusted users only.
- Consultation3.0 h
- Implementation8.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-9080 — 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-2018-9080 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