dbcve.org
Storcenter Px12 450r FirmwareOperating system · Lenovo

CVE-2018-9078

HIGH · 8.8 CVSS v3.0 Published 2018-09-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
For some Iomega, Lenovo, LenovoEMC NAS devices versions 4.1.402.34662 and earlier, the Content Explorer application grants users the ability to upload files to shares and this image was rendered in the browser in the device's origin instead of prompting to download the asset. The application does not prevent the user from uploading SVG images and returns these images within their origin. As a result, malicious users can upload SVG images that contain arbitrary JavaScript that is evaluated when the victim issues a request to download the file.

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 confidence

The Content Explorer application in Iomega, Lenovo, and LenovoEMC NAS devices (versions 4.1.402.34662 and earlier) allows users to upload files including SVG images without sanitization. Uploaded SVG files are rendered in the browser within the device's origin rather than being forced to download, enabling stored XSS via malicious JavaScript embedded in SVG files.

MitigationRestrict or disable SVG file uploads in Content Explorer, or implement server-side SVG sanitization to strip executable content before storage and delivery.

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
Storcenter Px12 450r FirmwareOperating system
Affected:= 4.1.402.34662
Storcenter Px12 400r FirmwareOperating system
Affected:= 4.1.402.34662
Storcenter Px4 300r FirmwareOperating system
Affected:= 4.1.402.34662
Storcenter Px6 300d FirmwareOperating system
Affected:= 4.1.402.34662
Storcenter Px4 300d FirmwareOperating system
Affected:= 4.1.402.34662
Storcenter Px2 300d FirmwareOperating system
Affected:= 4.1.402.34662
Storcenter Ix4 300d FirmwareOperating system
Affected:= 4.1.402.34662
Storcenter Ix2 FirmwareOperating system
Affected:= 4.1.402.34662

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the NAS device model
    Access the NAS device's web interface or use SSH to check the system model name. Look for model identifiers such as Storcenter Px12 450r, Px12 400r, Px4 300r, Px6 300d, Px4 300d, Px2 300d, Ix4 300d, or Ix2.
    Affected if The device is one of the listed Lenovo Storcenter or LenovoEMC models.
  2. Check the firmware version
    In the NAS web interface, navigate to System Settings or About section to view the firmware version. Alternatively, access the device via SSH and run: cat /etc/version or ls -la /firmware/version
    Affected if The firmware version is 4.1.402.34662 or earlier.
  3. Verify Content Explorer application is accessible
    Log into the NAS web interface and attempt to access the Content Explorer feature. Check if the application is enabled in the management console under Applications or Services.
    Affected if Content Explorer is enabled and accessible to users.
  4. Confirm file upload capability in Content Explorer
    Within Content Explorer, navigate to a folder and check if an upload option exists. Typically, look for an Upload button or drag-and-drop zone in the file manager interface.
    Affected if Users can upload files through the Content Explorer interface.
  5. Test SVG file handling behavior
    Upload a benign SVG file (or inspect the HTTP response headers when an SVG is requested) to determine if the browser renders it inline or forces a download. Check the Content-Type header - if it is image/svg+xml, the file is being rendered rather than downloaded.
    Affected if SVG files are served with Content-Type image/svg+xml and rendered in the browser instead of being forced to download.

A user is affected if their device is a Lenovo Storcenter or LenovoEMC NAS model running firmware version 4.1.402.34662 or earlier, with Content Explorer enabled and file upload functionality present that allows SVG files to be rendered in the browser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or disable SVG file uploads in Content Explorer, or implement server-side SVG sanitization to strip executable content before storage and delivery.

Fix this in Storcenter Px12 450r Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-9078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-9078 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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