Ez Media \& Backup Center Ix2 FirmwareOperating system · Lenovo

CVE-2019-19758

MEDIUM · 6.1 CVSS v3.1 Published 2020-02-14
Fix available
A fix is available. Upgrade to after 4.1.406.34763 or later.
See remediation →
68/100
Remediation priority · Elevated
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
A vulnerability in the web interface of Lenovo EZ Media & Backup Center, ix2 & ix2-dl version 4.1.406.34763 and prior could allow an unauthenticated, remote attacker to redirect a user to an untrusted web page.

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

This is an open redirect vulnerability in the web interface of Lenovo EZ Media & Backup Center and ix2/ix2-dl storage devices. An unauthenticated remote attacker can craft malicious URLs containing redirect parameters that cause the application's web interface to forward users to arbitrary external websites, potentially leading to phishing attacks or credential theft.

MitigationApply the vendor firmware update if available. If no update exists, consider restricting access to the web management interface via network segmentation or firewall rules to limit exposure to unauthenticated attackers.

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
Ez Media \& Backup Center Ix2 FirmwareOperating system
Affected:<= 4.1.406.34763
Ez Media \& Backup Center Ix2 Dl FirmwareOperating system
Affected:<= -4.1.406.34763

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

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

  1. Identify the device model
    Access the device's web interface or check the physical label to confirm the model is either Lenovo EZ Media & Backup Center, ix2, or ix2-dl storage device.
    Affected if The device is any of these three models.
  2. Check the firmware version
    Log into the device web interface and navigate to the System Settings or About page to view the installed firmware version. Compare this version against 4.1.406.34763.
    Affected if The firmware version is 4.1.406.34763 or lower.
  3. Verify web interface is accessible
    Attempt to access the device's web management interface over HTTP/HTTPS from a network location. Confirm the interface responds without authentication.
    Affected if The web interface is reachable without authentication on the network.
  4. Test for open redirect vulnerability
    Using a browser or curl, navigate to a URL on the device that includes a redirect parameter pointing to an external domain, such as: http://<device-ip>/cgi-bin/cgi?redirect=http://example.com. Observe if the application redirects to the external site.
    Affected if The application redirects to the arbitrary URL specified in the redirect parameter.

A user is affected if they have a Lenovo EZ Media & Backup Center, ix2, or ix2-dl device running firmware version 4.1.406.34763 or lower, with the web interface accessible over the network.

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
Upgrade available Upgrade to a release after 4.1.406.34763
Interim mitigation

Apply the vendor firmware update if available. If no update exists, consider restricting access to the web management interface via network segmentation or firewall rules to limit exposure to unauthenticated attackers.

Fix this in Ez Media \& Backup Center Ix2 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19758 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-19758 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