CVE-2005-1930
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 · uneditedDirectory traversal vulnerability in the Crystal Report component (rptserver.asp) in Trend Micro ServerProtect Management Console 5.58, as used in Control Manager 2.5 and 3.0 and Damage Cleanup Server 1.1, and possibly earlier versions, allows remote attackers to read arbitrary files via the IMAGE parameter.
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 confidenceDirectory traversal vulnerability in the Crystal Report component (rptserver.asp) of Trend Micro ServerProtect Management Console 5.58 allows remote attackers to read arbitrary files via a crafted IMAGE parameter. This path traversal attack enables attackers to access sensitive system files outside the intended web root directory.
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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Trend Micro ServerProtect Management Console is installedCheck for the presence of ServerProtect Management Console in installed programs (Windows Add/Remove Programs) or look for the installation directory, typically under C:\Program Files\Trend Micro\ServerProtect\ or similar paths.Affected if The product is not installed, the vulnerability does not apply.
-
Confirm the installed version is exactly 5.58Open the Management Console and navigate to Help > About, or check the version in the Windows installed programs list. Alternatively, check the version info of the main executable (e.g., splash.exe or SProtectSvr.exe) in the installation directory.Affected if The version is NOT 5.58, the specific CVE does not apply (though other vulnerabilities may exist).
-
Determine if the Crystal Report component (rptserver.asp) is accessibleAttempt to access the URL pattern: http://[server]:[port]/sppc/rptserver.asp or similar paths under the Management Console web interface. Check IIS or the web server configuration for the presence of the /sppc/ virtual directory.Affected if The rptserver.asp file is not present or not accessible via web, the vulnerability cannot be exploited.
-
Verify if the web interface accepts the IMAGE parameter via GET or POSTSend a test request with a crafted IMAGE parameter to rptserver.asp, such as: GET /sppc/rptserver.asp?IMAGE=../../../../../../../../winnt/win.ini. Check if the response contains file contents or an error revealing file access capability.Affected if The IMAGE parameter is not processed or the path traversal is blocked, the specific attack vector is not viable.
A defender is affected only if Trend Micro ServerProtect Management Console version 5.58 is installed, the rptserver.asp Crystal Report component is web-accessible, and the IMAGE parameter accepts path traversal sequences.
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 if available; if no patch exists, restrict network access to the vulnerable rptserver.asp component or disable the Crystal Report functionality entirely; consider upgrading to supported product versions as legacy systems may lack security updates.
- 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-2005-1930 — 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-1930 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