CVE-2007-3132
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 · uneditedMultiple vulnerabilities in Symantec Ghost Solution Suite 2.0.0 and earlier, with Ghost 8.0.992 and possibly other versions, allow remote attackers to cause a denial of service (client or server crash) via malformed requests to the daemon port, 1346/udp or 1347/udp.
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 2.0.0 and Ghost 8.0.992 contain multiple vulnerabilities in their daemon service listening on UDP ports 1346 and 1347. Remote attackers can send malformed UDP packets to these ports, causing either the Ghost client or server to crash, resulting in denial of service.
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= 8.0CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Verify if Symantec Ghost is installedCheck the system for installed software named 'Symantec Ghost', 'Norton Ghost', or 'Ghost Solution Suite' via Add/Remove Programs, or search for ghost.exe in program directories.Affected if The software is present on the system.
-
Identify the installed Ghost versionLocate the Ghost executable (typically in C:\Program Files\Symantec\Ghost or similar) and check its version properties, or use the command 'ghost -ver' if the CLI is available.Affected if The version is 8.0 (specifically 8.0.992) or the Ghost Solution Suite version is 2.0.0 or lower.
-
Check if UDP ports 1346 or 1347 are listeningRun 'netstat -an | findstr "1346\|1347"' or use a port scanner to determine if UDP ports 1346 and 1347 are open and listening on the machine.Affected if Either UDP port 1346 or 1347 is in a LISTENING state.
-
Confirm the Ghost service is runningCheck Windows Services for 'Ghost' or 'Symantec Ghost' service status, or verify the ghost.exe process is active via Task Manager.Affected if The Ghost service or process is currently running.
A user is affected if Symantec Ghost Solution Suite <= 2.0 or Norton Ghost 8.0 is installed with the daemon service running and UDP ports 1346/1347 listening, as this exposes the system to the denial-of-service vulnerability.
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 dataRestrict network access to UDP ports 1346 and 1347 via firewall rules or network segmentation to prevent unauthorized external sources from reaching the Ghost service. If a patched version is available from Symantec, upgrade the software.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3132 — 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-3132 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