dbcve.org
OfficescanApplication · Trend Micro

CVE-2006-6458

HIGH · 7.8 CVSS v2.0 Published 2006-12-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
The Trend Micro scan engine before 8.320 for Windows and before 8.150 on HP-UX and AIX, as used in Trend Micro PC Cillin - Internet Security 2006, Office Scan 7.3, and Server Protect 5.58, allows remote attackers to cause a denial of service (CPU consumption and system hang) via a malformed RAR archive with an Archive Header section with the head_size and pack_size fields set to zero, which triggers an infinite loop.

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

A vulnerability in the Trend Micro scan engine (versions before 8.320 on Windows and before 8.150 on HP-UX/AIX) allows remote attackers to cause denial of service by sending malformed RAR archives. The malformed archive contains an Archive Header section with head_size and pack_size fields set to zero, which triggers an infinite loop in the scan engine leading to CPU consumption and system hang.

MitigationUpdate the Trend Micro scan engine to version 8.320 or later for Windows, or 8.150 or later for HP-UX/AIX. Consider implementing network-level filtering to block suspicious RAR file attachments until the update can be applied.

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
OfficescanApplication
Affected:= 7.3
Pc Cillin Internet Security 2006Application
Affected:all versions
ServerprotectApplication
Affected:= 5.58

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
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/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. Identify installed Trend Micro product
    Check Programs and Features (Windows) or use 'swlist' command (HP-UX/AIX) to list installed Trend Micro software. Look for Officescan, Pc Cillin Internet Security 2006, or ServerProtect.
    Affected if Any of these three products are installed
  2. Check product version
    Right-click the Trend Micro icon in system tray and select 'About' or open the product console and navigate to the version information section. Compare against: Officescan 7.3, Pc Cillin Internet Security 2006 (any version), ServerProtect 5.58.
    Affected if The installed product matches one of these versions or is an earlier version of the same product line
  3. Determine scan engine version
    Open the Trend Micro product console, go to Settings or Help > About. Look for 'Scan Engine' or 'Engine Version' information. On Windows, this may also be found in the registry under HKLM\SOFTWARE\TrendMicro\ScanEngine or within the product's program folder.
    Affected if Scan engine version is below 8.320 (Windows) or below 8.150 (HP-UX/AIX)
  4. Confirm real-time or manual scan is enabled
    Open the Trend Micro product console and check the status of 'Real-time Scan', 'Manual Scan', or 'Scheduled Scan' features. Verify if these scanning features are turned on or enabled.
    Affected if Any scanning feature that can process RAR attachments is active; the vulnerability triggers when the scan engine attempts to parse a malformed RAR file

The environment is affected if a vulnerable Trend Micro product (Officescan 7.3, Pc Cillin 2006, or ServerProtect 5.58) with a scan engine version below 8.320 (Windows) or below 8.150 (HP-UX/AIX) has scanning capabilities enabled that would process incoming RAR archives.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Trend Micro scan engine to version 8.320 or later for Windows, or 8.150 or later for HP-UX/AIX. Consider implementing network-level filtering to block suspicious RAR file attachments until the update can be applied.

Fix this in Officescan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-6458 — 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-2006-6458 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