CVE-2007-1173
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 buffer overflows in the CentennialIPTransferServer service (XFERWAN.EXE), as used by (1) Centennial Discovery 2006 Feature Pack 1, (2) Numara Asset Manager 8.0, and (3) Symantec Discovery 6.5, allow remote attackers to execute arbitrary code via long strings in a crafted TCP packet.
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 confidenceBuffer overflow vulnerability in the CentennialIPTransferServer service (XFERWAN.EXE) allows remote attackers to execute arbitrary code by sending crafted TCP packets containing overly long strings. This affects multiple discovery/asset management products from Centennial, Numara, and Symantec.
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= 2006_featurepack1= 8.0= 6.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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/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 if XFERWAN.EXE service is runningOn Windows, open Task Manager or run 'tasklist /SVC' in command prompt and look for XFERWAN.EXE process, or check Windows Services for 'CentennialIPTransferServer' serviceAffected if The XFERWAN.EXE process or CentennialIPTransferServer service is running on the system
-
Determine installed product versionCheck the installed version of Centennial Discovery, Numara Asset Manager, or Symantec Discovery by reviewing the application in Add/Remove Programs, the program directory, or the program's About/Help informationAffected if The installed version matches Centennial Discovery 2006_featurepack1, Numara Asset Manager 8.0, or Symantec Discovery 6.5
-
Identify TCP port listener for XFERWAN serviceRun 'netstat -an' or use a network port scanner to identify which TCP port XFERWAN.EXE is listening on (the service accepts inbound TCP connections)Affected if XFERWAN.EXE is bound to a listening TCP port on the system
-
Verify network exposure of the serviceCheck firewall rules and network configuration to determine if the XFERWAN TCP port is accessible from external networks or untrusted systemsAffected if The XFERWAN service port is accessible from network segments outside the trusted internal network
A system is affected if it runs XFERWAN.EXE (CentennialIPTransferServer service) from one of the affected product versions (Centennial Discovery 2006 FP1, Numara Asset Manager 8.0, or Symantec Discovery 6.5) and that service is network-accessible.
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 vendor patches for the affected products (Centennial Discovery 2006 FP1, Numara Asset Manager 8.0, Symantec Discovery 6.5), or if patches are unavailable, disable the XFERWAN.EXE service and block the affected TCP port at the network perimeter.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1173 — 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-1173 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