CVE-2005-1929
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 heap-based buffer overflows in (1) isaNVWRequest.dll and (2) relay.dll in Trend Micro ServerProtect Management Console 5.58 and earlier, as used in Control Manager 2.5 and 3.0 and Damage Cleanup Server 1.1, allow remote attackers to execute arbitrary code via "wrapped" length values in Chunked transfer requests. NOTE: the original report suggests that the relay.dll issue is related to a problem in which a Microsoft Foundation Classes (MFC) static library returns invalid values under heavy load. As such, this might not be a vulnerability in Trend Micro's product.
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 confidenceHeap-based buffer overflow vulnerabilities in Trend Micro ServerProtect Management Console 5.58 and earlier allow remote attackers to execute arbitrary code via crafted Chunked transfer requests containing 'wrapped' length values. The overflows occur in isaNVWRequest.dll and relay.dll components used by Control Manager and Damage Cleanup Server.
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<= 5.58CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Identify if Trend Micro ServerProtect is installedCheck for the ServerProtect installation directory (commonly at C:\Program Files\Trend Micro\ServerProtect or C:\Program Files\Trend Micro\ServerProtect Management Console). Also look for ServerProtect services in Windows Services (spnt.exe or similar processes).Affected if ServerProtect software is found on the system
-
Determine the installed version of ServerProtectCheck the version of the ServerProtect executable or DLL. Look at file properties of spnt.exe, ServerProtect.exe, or the Management Console components. Compare the version number to 5.58 - any version <= 5.58 is affected.Affected if The installed version is 5.58 or earlier
-
Verify the Management Console component is presentCheck for the presence of isaNVWRequest.dll and relay.dll in the ServerProtect installation directory (typically in the Common or bin folder). These DLLs contain the vulnerability.Affected if Both isaNVWRequest.dll and relay.dll are present in the ServerProtect installation
-
Confirm the Management Console service is accessibleCheck if the ServerProtect Management Console service (typically listening on TCP port 80/443 or specific ports like 8080) is running and exposed. Look for the service in Windows Services and check for listening network ports.Affected if The Management Console service is running and accessible on the network
A system is affected if Trend Micro ServerProtect version 5.58 or earlier is installed with the Management Console component (isaNVWRequest.dll and relay.dll) present and 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 dataGiven this is 2005-era software, the primary remediation is to upgrade to a supported version or, if upgrade is not feasible, isolate affected systems from untrusted network access and implement network segmentation to reduce exposure.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1929 — 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-2005-1929 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