CVE-2018-9080: Iomega and LenovoEMC NAS Web UI Vulnerabilities
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.72% (FIRST EPSS); higher than 54.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
For 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.
- Published
- Sep 28, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- CWE-287
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| lenovo | storcenter px12-450r firmware | cpe:2.3:o:lenovo:storcenter_px12-450r_firmware |
| lenovo | storcenter px12-450r | cpe:2.3:h:lenovo:storcenter_px12-450r |
| lenovo | storcenter px12-400r firmware | cpe:2.3:o:lenovo:storcenter_px12-400r_firmware |
| lenovo | storcenter px12-400r | cpe:2.3:h:lenovo:storcenter_px12-400r |
| lenovo | storcenter px4-300r firmware | cpe:2.3:o:lenovo:storcenter_px4-300r_firmware |
| lenovo | storcenter px4-300r | cpe:2.3:h:lenovo:storcenter_px4-300r |
| lenovo | storcenter px6-300d firmware | cpe:2.3:o:lenovo:storcenter_px6-300d_firmware |
| lenovo | storcenter px6-300d | cpe:2.3:h:lenovo:storcenter_px6-300d |
| lenovo | storcenter px4-300d firmware | cpe:2.3:o:lenovo:storcenter_px4-300d_firmware |
| lenovo | storcenter px4-300d | cpe:2.3:h:lenovo:storcenter_px4-300d |
| lenovo | storcenter px2-300d firmware | cpe:2.3:o:lenovo:storcenter_px2-300d_firmware |
| lenovo | storcenter px2-300d | cpe:2.3:h:lenovo:storcenter_px2-300d |
and 28 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (lenovo). Independent of NVD's CPE analysis and usually ahead of it.
Lenovo Group LTD EZ Media and Backup Center
- 4.1.402.34662 and later · up to and including 4.1.402.34662affected
Lenovo Group LTD Iomega StorCenter
- 4.1.402.34662 and later · up to and including 4.1.402.34662affected
Lenovo Group LTD LenovoEMC
- 4.1.402.34662 and later · up to and including 4.1.402.34662affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo ez media & backup center firmware4.1.402.34662
- lenovo ix2 firmware4.1.402.34662
- lenovo ix4-300d firmware4.1.402.34662
- lenovo px12-400r firmware4.1.402.34662
- lenovo px12-450r firmware4.1.402.34662
- lenovo px2-300d firmware4.1.402.34662
- lenovo px4-300d firmware4.1.402.34662
- lenovo px4-300r firmware4.1.402.34662
- lenovo px4-400d firmware4.1.402.34662
- lenovo px4-400r firmware4.1.402.34662
- lenovo px6-300d firmware4.1.402.34662
- lenovo storcenter ix2 firmware4.1.402.34662
- lenovo storcenter ix2-dl firmware4.1.402.34662
- lenovo storcenter ix4-300d firmware4.1.402.34662
- lenovo storcenter px12-400r firmware4.1.402.34662
- lenovo storcenter px12-450r firmware4.1.402.34662
- lenovo storcenter px2-300d firmware4.1.402.34662
- lenovo storcenter px4-300d firmware4.1.402.34662
- lenovo storcenter px4-300r firmware4.1.402.34662
- lenovo storcenter px6-300d firmware4.1.402.34662
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-9079Iomega and LenovoEMC NAS Web UI Vulnerabilities39Monitor
- CVE-2018-9082Iomega and LenovoEMC NAS Web UI Vulnerabilities35Monitor
- CVE-2018-9078Iomega and LenovoEMC NAS Web UI Vulnerabilities35Monitor
Published before and after this one in the same product
- Later →CVE-2018-9081Sep 28, 2018 · Iomega and LenovoEMC NAS Web UI Vulnerabilities18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.