CVE-2001-1026
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 · uneditedTrend Micro InterScan AppletTrap 2.0 does not properly filter URLs when they are modified in certain ways such as (1) using a double slash (//) instead of a single slash, (2) URL-encoded characters, (3) requesting the IP address instead of the domain name, or (4) using a leading 0 in an octet of an IP address.
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 confidenceTrend Micro InterScan AppletTrap 2.0 fails to properly normalize and filter URLs containing certain variations, allowing attackers to bypass security controls. The vulnerability can be exploited by using double slashes (//) instead of single slashes, URL-encoded characters, direct IP addresses instead of domain names, or leading zeros in IP octets.
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= 2.0CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Trend Micro InterScan AppletTrap is installedCheck for the AppletTrap service or process on the system. Look in Windows Services for 'InterScan AppletTrap' or check for the installation directory typically at C:\Program Files\Trend Micro\InterScan AppletTrap or similar. Also check Add/Remove Programs for the application.Affected if The application is installed on the system
-
Verify the installed version is 2.0Check the version of the installed InterScan AppletTrap. Look in the Windows Registry under HKLM\SOFTWARE\TrendMicro\InterScanAppletTrap for a Version value, or check the version property of the main executable file (often named applettrap.exe or similar in the installation directory.Affected if The installed version is exactly 2.0 (note: other versions are not affected by this specific CVE)
-
Confirm URL filtering feature is enabledCheck the AppletTrap configuration for URL filtering settings. Look in the management console or configuration files for 'URL Filter' or 'Web security' settings. Verify the service is running and URL blocking is actively configured.Affected if URL filtering feature is enabled and the service is running (the bypass only matters if filtering is in use)
You are affected only if Trend Micro InterScan AppletTrap version 2.0 is installed with URL filtering functionality enabled, as the vulnerability allows bypassing that specific security control.
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 Trend Micro InterScan or implement upstream URL normalization at proxies/firewalls to canonicalize URLs before they reach the vulnerable application.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-1026 — 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-2001-1026 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