dbcve.org
ServerprotectApplication · Trend Micro

CVE-2007-6507

HIGH · 10.0 CVSS v2.0 Published 2007-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SpntSvc.exe daemon in Trend Micro ServerProtect 5.58 for Windows, before Security Patch 4, exposes unspecified dangerous sub-functions from StRpcSrv.dll in the DCE/RPC interface, which allows remote attackers to obtain "full file system access" and execute arbitrary code.

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 confidence

The SpntSvc.exe daemon in Trend Micro ServerProtect 5.58 for Windows exposes dangerous sub-functions from StRpcSrv.dll through its DCE/RPC interface without proper authentication or authorization controls. This allows unauthenticated remote attackers to gain full file system access and execute arbitrary code with SYSTEM-level privileges.

MitigationApply Trend Micro Security Patch 4 (or upgrade to a supported version) to the ServerProtect installation to remediate the vulnerable RPC interface exposure.

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
ServerprotectApplication
Affected:= 5.58_security_patch_3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Trend Micro ServerProtect is installed
    Check the system for presence of ServerProtect software in installed programs or check for ServerProtect installation directory
    Affected if ServerProtect is not present on the system - no further action needed
  2. Confirm installed version is 5.58_security_patch_3
    Locate and inspect the version of ServerProtect - typically visible in Add/Remove Programs, the product GUI, or version resource of SpntSvc.exe
    Affected if The installed version is exactly 5.58_security_patch_3 (this specific version is listed as affected)
  3. Verify SpntSvc.exe service is running
    Check Windows services or task list for SpntSvc.exe process - the daemon that contains the vulnerable StRpcSrv.dll component
    Affected if SpntSvc.exe service is actively running (the vulnerable component is in use)
  4. Check if DCE/RPC interface is network-accessible
    Network scan for exposed RPC endpoints (port 135 or dynamic ports 1025+) or verify the ServerProtect RPC service binding is accessible without authentication
    Affected if The DCE/RPC interface is exposed to the network and accepts unauthenticated requests

System is affected only if ServerProtect version 5.58_security_patch_3 is installed with SpntSvc.exe running and its unauthenticated DCE/RPC interface is accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Trend Micro Security Patch 4 (or upgrade to a supported version) to the ServerProtect installation to remediate the vulnerable RPC interface exposure.

Recommended fix Moderate confidence

Trend Micro ServerProtect 5.58 Security Patch 4

  1. Verify the current installed version of Trend Micro ServerProtect by checking the SpntSvc.exe service version or the program files version
  2. Download Security Patch 4 for Trend Micro ServerProtect 5.58 from the official Trend Micro download center or support website
  3. Apply Security Patch 4 following the standard Trend Micro patch installation procedure
  4. Verify that the patch was successfully applied by checking the version again
  5. Restart the SpntSvc.exe service if not automatically restarted by the patch installer
Caveat Review Trend Micro release notes for Security Patch 4 to confirm compatibility with your environment and any known issues

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Serverprotect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-6507 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-6507 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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