CVE-2013-2342
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 HP StoreOnce D2D backup system with software before 3.0.0 has a default password of badg3r5 for the HPSupport account, which allows remote attackers to obtain administrative access and delete data via an SSH session.
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 HP StoreOnce D2D backup system versions prior to 3.0.0 contain a hardcoded default password (badg3r5) for the HPSupport account. Attackers can exploit this by initiating an SSH session using these default credentials to gain administrative access and potentially delete backup data.
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<= 2.2.17= 2.1.01= 2.2.00= 2.2.10= 2.2.13= 2.2.14= 2.2.16CVSS 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
- Adjacent
- Complexity
- Low
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:L/Au:S/C:C/I:C/A:C
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 installed HP StoreOnce D2D versionAccess the D2D system management interface or use the command line tool to retrieve the software version number. This is typically found in the system settings or via the 'show version' command if accessible via SSH or console.Affected if The installed version matches one of the affected versions: <= 2.2.17, 2.1.01, 2.2.00, 2.2.10, 2.2.13, 2.2.14, or 2.2.16.
-
Verify if SSH access is enabled on the systemCheck the D2D system configuration settings to confirm whether the SSH service is enabled and accessible from the network. Look for SSH settings in the management interface or check if port 22 is listening.Affected if SSH is enabled and the system is network-accessible, providing an attack vector for the default credential exploit.
-
Confirm the HPSupport account exists and uses the default passwordAttempt to authenticate via SSH using the username 'HPSupport' with the password 'badg3r5', or check the local account configuration if you have administrative access to the system.Affected if The HPSupport account is present and the default password 'badg3r5' is still in use.
You are affected if your HP StoreOnce D2D version is in the affected list and the HPSupport account still has its default password 'badg3r5' with SSH access enabled.
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 dataImmediately change the default password for the HPSupport account to a strong, unique password and upgrade to software version 3.0.0 or later to resolve this vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2342 — 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-2013-2342 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