CVE-2002-2394
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 · uneditedInterScan VirusWall 3.6 for Linux and 3.52 for Windows allows remote attackers to bypass virus protection and possibly execute arbitrary code via HTTP 1.1 chunked transfer encoding.
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 confidenceInterScan VirusWall 3.6 for Linux and 3.52 for Windows fails to properly scan HTTP requests using chunked transfer encoding, allowing malicious payloads to bypass virus detection and potentially execute arbitrary code on the protected system.
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= 3.6= 3.52CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 InterScan VirusWall installationLocate the InterScan VirusWall installation directory or check installed packages. On Linux, look for /opt/trend or review RPM/DPKG packages. On Windows, check Add/Remove Programs or the installation path (typically C:\Program Files\Trend Micro\).Affected if InterScan VirusWall is present on the system
-
Determine installed version numberCheck the version of the installed InterScan VirusWall. On Linux, run 'ismg' or look in the version file within the installation directory. On Windows, right-click the executable and view Properties, or check the registry under the Trend Micro installation key.Affected if Version equals 3.6 (Linux) or 3.52 (Windows)
-
Confirm HTTP scanning is enabledAccess the InterScan VirusWall configuration interface or check the configuration files for the HTTP scanner module. Verify that HTTP scanning is turned on and active.Affected if HTTP virus scanning is enabled and active
-
Check HTTP proxy listening statusVerify that the InterScan VirusWall HTTP proxy service is running and listening on the configured port (typically port 8080 or 3128). Use 'netstat' or 'ps' commands to confirm the service is active.Affected if HTTP proxy service is running and accepting connections
The environment is affected if InterScan VirusWall version 3.6 or 3.52 is installed with HTTP scanning enabled, allowing chunked transfer encoded HTTP requests to bypass virus detection.
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 dataUpgrade to a patched version of InterScan VirusWall or migrate to a current Trend Micro security solution that properly handles HTTP 1.1 chunked transfer encoding in its virus scanning engine.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2002-2394 — 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-2002-2394 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