CVE-2012-0306
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 Ghost Solution Suite 2.x through 2.5.1 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted backup file.
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 · moderate confidenceSymantec Ghost Solution Suite versions 2.x through 2.5.1 contains a memory corruption vulnerability in its backup file parsing functionality. Attackers can exploit this by crafting malicious backup files, potentially achieving remote code execution or causing denial of service. The vulnerability stems from improper handling of malformed backup file structures.
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.0= 2.0.0= 2.0.1= 2.5CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Confirm Ghost Solution Suite installationCheck for Ghost installation by searching for executable files named 'ghost.exe' or 'gdisk.exe' in common installation paths such as C:\Program Files\Symantec\Ghost, or check Windows Registry under HKLM\SOFTWARE\Symantec\Ghost for installation keys.Affected if Symantec Ghost Solution Suite is found installed on the system.
-
Identify installed versionLocate the Ghost executable (commonly at C:\Program Files\Symantec\Ghost\ghost.exe) and check its file properties for version information, or query the Windows Registry key HKLM\SOFTWARE\Symantec\Ghost\Common\InstallDir for the installation path, then read version details from the executable.Affected if The installed version falls within 2.0 through 2.5.1.
-
Verify backup parsing functionality is in useReview system tasks, scheduled tasks, or scripts that invoke Ghost for backup or imaging operations. Check for .gho or .v2i backup file extensions being processed, or examine any configuration files that define backup jobs.Affected if The system uses Ghost to process backup or imaging files.
-
Inspect backup file locations for anomaliesExamine directories where Ghost stores or processes backup files (typically .gho, .v2i, or related backup image files) for unexpectedly large files, files with unusual headers, or files lacking proper file structure.Affected if Malformed or suspicious backup files are present in directories accessed by Ghost.
A user is affected if Symantec Ghost Solution Suite versions 2.0 through 2.5.1 is installed and the backup file parsing functionality is actively used to process backup images.
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 dataApply available vendor patches for Symantec Ghost Solution Suite. If patches are unavailable for this legacy product, restrict access to the Ghost infrastructure, validate all backup files before processing, and consider migrating to a supported solution.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0306 — 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-0306 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