Scalar I500 FirmwareApplication · Quantum

CVE-2012-1841

MEDIUM · 5.0 CVSS v2.0 Published 2012-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Absolute path traversal vulnerability in logShow.htm on the Quantum Scalar i500 tape library with firmware before i7.0.3 (604G.GS00100), also distributed as the Dell ML6000 tape library with firmware before A20-00 (590G.GS00100), allows remote attackers to read arbitrary files via a full pathname in the file parameter.

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

Absolute path traversal vulnerability in logShow.htm web script on Quantum Scalar i500 and Dell ML6000 tape libraries allows remote attackers to read arbitrary files from the filesystem by supplying a full pathname in the 'file' parameter, without proper input validation.

MitigationUpdate firmware to version i7.0.3 or later for Quantum Scalar i500, or A20-00 or later for Dell ML6000. If patching is not immediately possible, consider network segmentation to restrict access to the tape library management interface.

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
Scalar I500 FirmwareApplication
Affected:<= i7.0.2= i2= i3= i3.1= i4= i5= i5.1= i6= i6.1= i7= i7.0.1= sp4
Scalar I500Hardware / appliance
Affected:= 5u= 14u= 23u
Powervault Ml6000 FirmwareApplication
Affected:= 585g.gs003
Powervault Ml6000Hardware / appliance
Affected:= 32u= 41u
Powervault Ml6010Hardware / appliance
Affected:= 5u
Powervault Ml6020Hardware / appliance
Affected:= 14u
Powervault Ml6030Hardware / appliance
Affected:= 23u

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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 tape library model
    Access the device's web management interface or check the physical device label/model number. Look for Quantum Scalar i500 or Dell Powervault ML6000/ML6010/ML6020/ML6030 designations.
    Affected if The device is NOT one of these models: Quantum Scalar I500, Dell Powervault ML6000, ML6010, ML6020, or ML6030.
  2. Check Quantum Scalar i500 firmware version
    Log into the Quantum Scalar i500 web interface and navigate to the System Status or About section to view the firmware version.
    Affected if The firmware version is i2, i3, i3.1, i4, i5, i5.1, i6, i6.1, i7, i7.0.1, i7.0.2, or sp4 (any version <= i7.0.2).
  3. Check Dell ML6000 firmware version
    Log into the Dell Powervault ML6000 web interface and navigate to the System Status or About section to view the firmware version.
    Affected if The firmware version is 585g.gs003.
  4. Verify web interface accessibility
    Attempt to access the logShow.htm script by navigating to http(s)://[device-ip]/logShow.htm in a web browser.
    Affected if The logShow.htm page loads successfully and accepts a 'file' parameter.
  5. Test path traversal vulnerability
    Submit a request with a full pathname in the file parameter, such as: http(s)://[device-ip]/logShow.htm?file=/etc/passwd or http(s)://[device-ip]/logShow.htm?file=C:\Windows\win.ini
    Affected if The server returns the contents of an arbitrary file from the filesystem instead of rejecting the request.

A user is affected if they have a Quantum Scalar i500 with firmware <= i7.0.2 or a Dell ML6000 series with firmware 585g.gs003, and the web management interface with logShow.htm is accessible and accepts arbitrary file paths in the 'file' parameter.

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

Update firmware to version i7.0.3 or later for Quantum Scalar i500, or A20-00 or later for Dell ML6000. If patching is not immediately possible, consider network segmentation to restrict access to the tape library management interface.

Fix this in Scalar I500 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-1841 — 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-2012-1841 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