Interscan Messaging Security SuiteApplication · Trend Micro

CVE-2006-0642

MEDIUM · 5.1 CVSS v2.0 Published 2006-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Trend Micro ServerProtect 5.58, and possibly InterScan Messaging Security Suite and InterScan Web Security Suite, have a default configuration setting of "Do not scan compressed files when Extracted file count exceeds 500 files," which may be too low in certain circumstances, which allows remote attackers to bypass anti-virus checks by sending compressed archives containing many small files. NOTE: since this is related to a configuration setting that has an operational impact that might vary depending on the environment, and the product is claimed to report a message when the compressed file exceeds specified limits, perhaps this should not be included in CVE.

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

Trend Micro ServerProtect 5.58 and related products have a default configuration threshold that stops scanning compressed files when they contain more than 500 extracted files. This threshold can be exploited by remote attackers who craft archives with many small files to bypass anti-virus detection.

MitigationIncrease the 'Extracted file count' threshold in the product configuration to a value appropriate for the environment, or disable this limit for high-security zones.

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
Interscan Messaging Security SuiteApplication
Affected:all versions
Interscan Web Security SuiteApplication
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
High
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:H/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 checks

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

  1. Identify installed Trend Micro product
    Review installed software on the system to determine if Trend Micro Interscan Messaging Security Suite, Trend Micro Interscan Web Security Suite, or Trend Micro ServerProtect 5.58 is present
    Affected if Any of these products is installed, the environment may be vulnerable
  2. Locate the Extracted file count threshold setting
    Access the product configuration console or configuration files for the installed Trend Micro product and locate the setting related to 'Extracted file count' or 'Maximum extracted files' threshold for archive scanning
    Affected if The setting exists and is currently configured at the default threshold of 500 files
  3. Verify the current threshold value
    Examine the current value of the Extracted file count threshold configuration setting
    Affected if The threshold is set to 500 (the default vulnerable value) or remains at the default setting without being explicitly increased
  4. Check if archive scanning is enabled
    Confirm that compressed file scanning or archive scanning features are enabled in the product configuration
    Affected if Archive scanning is enabled AND the extracted file count threshold remains at the default 500 value, the product can be bypassed by archives containing more than 500 files

A system is affected if it runs any of the listed Trend Micro products with the default Extracted file count threshold of 500 still in place and archive scanning enabled.

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

Increase the 'Extracted file count' threshold in the product configuration to a value appropriate for the environment, or disable this limit for high-security zones.

Fix this in Interscan Messaging Security Suite 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-0642 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-0642 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