CVE-2007-2360
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 · uneditedSymantec Norton Ghost, Norton Save & Recovery, LiveState Recovery, and BackupExec System Recovery before 20070426, when remote backups of restore point images are configured, encrypt network share credentials with a key formed by a hash of the username, which allows local users to obtain the credentials by calculating the key.
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 confidenceWhen remote backups of restore point images are configured in Symantec Norton Ghost, Norton Save & Recovery, LiveState Recovery, and BackupExec System Recovery (versions before 20070426), network share credentials are encrypted using a weak key derived solely from a hash of the username. Local users can reverse-engineer this key and obtain plaintext credentials.
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= 6.5= 6.52= 6.52a= 6.53= 6.0= 6.01= 6.02= 10.0= 10.01= 1.01= 1.01b= 11.0= 11.01= 11.01bCVSS 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
- Local
- Complexity
- Low
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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 installed Symantec backup product and versionCheck Windows Registry under HKLM\SOFTWARE\Symantec\ or look at executable file properties for Ghost.exe, SaveAndRecovery.exe, LiveStateRecovery.exe, or BackupExecSystemRecovery.exe. Also check Add/Remove Programs for these product names.Affected if The installed version matches one of these: BackupExec System Recovery 6.5, 6.52, 6.52a, or 6.53; LiveState Recovery 6.0, 6.01, or 6.02; Norton Ghost 10.0 or 10.01; Norton Save And Recovery 1.01, 1.01b, 11.0, 11.01, or 11.01b.
-
Check for configured network share backup jobsLook for backup job definitions or scheduled tasks created by these products that point to UNC paths (\\server\share) or mapped network drives. Check the product's GUI for existing backup definitions, or look in the product's data directory for .gho, .bkf, or configuration files referencing network locations.Affected if Any backup job or restore point image is configured to store to or retrieve from a network share.
-
Locate stored network share credentialsSearch the product's configuration or data directories for files that may contain encrypted credentials, such as .cfg, .ini, .dat, or registry export files. On Windows, also check the registry under HKCU\SOFTWARE\Symantec\ for stored credential references.Affected if Credential files or registry entries exist that contain encrypted network share authentication data for these products.
A system is affected if it runs any of the listed unpatched versions AND has network share backup credentials stored locally, because the vulnerability only exposes credentials used for remote backup configurations.
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 dataUpgrade to patched versions (post-20070426) or migrate to current supported versions of the backup/recovery products. If legacy systems cannot be upgraded, restrict local access and monitor for credential access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2360 — 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-2007-2360 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