CVE-2012-1844
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 · uneditedThe 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) and the IBM TS3310 tape library with firmware before R6C (606G.GS001), uses default passwords for unspecified user accounts, which makes it easier for remote attackers to obtain access via unknown vectors.
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 confidenceThe Quantum Scalar i500 tape library (also sold as Dell ML6000 and IBM TS3310) ships with default passwords for certain user accounts in firmware versions prior to i7.0.3 (Quantum), A20-00 (Dell), and R6C (IBM). These well-known credentials allow remote attackers to authenticate to the device's management interface without requiring any other vulnerability.
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<= i7.0.2= i2= i3= i3.1= i4= i5= i5.1= i6= i6.1= i7= i7.0.1= sp4= 5u= 14u= 23u= 585g.gs003= 32u= 41u= 5u= 14u= 23u<= 605g.g002CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 the tape library modelAccess the device's web management interface or check the physical device label to confirm the model: Quantum Scalar i500, Dell ML6000/ML6010/ML6020/ML6030, or IBM TS3310Affected if The device is any of these models and is reachable on the network
-
Check the installed firmware versionLog into the device's management interface and navigate to the firmware or system information section. Record the exact firmware version string (such as i7.0.2, 585g.gs003, or 605g.g002)Affected if The firmware version matches one listed in the affected versions (for Quantum: i7.0.2 or earlier, i2-i7.0.1, sp4; for Dell: 585g.gs003; for IBM: 605g.g002 or earlier)
-
Verify default credentials are still in useAttempt to access the management interface using the well-known default credentials for the device (these are publicly documented in CVE-2012-1844 references). If authentication succeeds without password change, default credentials are activeAffected if Default administrative passwords have not been changed from their factory defaults, allowing unauthenticated remote access
The environment is affected if the device is a Quantum Scalar i500, Dell ML6000 series, or IBM TS3310 tape library running any of the vulnerable firmware versions listed AND default passwords remain unchanged on the admin accounts.
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 dataChange all default passwords immediately on affected devices and update firmware to the patched versions (i7.0.3, A20-00, or R6C respectively). Network segmentation should be applied to restrict management interface access to authorized administrative hosts.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1844 — 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-2012-1844 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