CVE-2007-5437
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 · uneditedThe web console in CA (formerly Computer Associates) eTrust ITM (Threat Manager) 8.1 allows remote attackers to redirect users to arbitrary web sites via a crafted HTTP URL on port 6689.
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 confidenceCA eTrust ITM (Threat Manager) 8.1 web console contains an open redirect vulnerability (CWE-601) on port 6689. Attackers can craft malicious HTTP URLs to redirect authenticated users to arbitrary external websites, enabling phishing attacks.
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= 8.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:N/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 CA eTrust ITM is installedCheck system for CA eTrust ITM installation directories or the eTrust ITM/Threat Manager service. Common locations include C:\Program Files\CA\eTrust ITM or /opt/CA/eTrustITM on Unix systems. Look for the 'eTrust ITM' or 'Threat Manager' Windows service.Affected if CA eTrust ITM (Threat Manager) software is present on the system
-
Verify the installed version is 8.1Locate the product version information. Check the About dialog in the application, look for version files in the installation directory, or query the installed software registry keys on Windows (HKLM\SOFTWARE\ComputerAssociates\eTrust ITM).Affected if The installed version is exactly 8.1 (no patches applied)
-
Check if web console is running on port 6689Verify that the eTrust ITM web console service is listening on port 6689. Use netstat -an | findstr 6689 or ss -tlnp | grep 6689 to check for listening ports, or attempt a local HTTP connection to http://localhost:6689.Affected if The web console service is accessible and listening on port 6689
-
Test for open redirect vulnerabilitySend a crafted HTTP request to the web console with a malicious redirect parameter. For example: http://localhost:6689/login?url=http://malicious-site.com. Observe if the application accepts and reflects an external URL in a redirect response.Affected if The web console accepts arbitrary external URLs in redirect parameters without validation
A system is affected if CA eTrust ITM version 8.1 is installed with the web console service running on port 6689 and the application accepts unvalidated external URLs as redirect targets.
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 dataApply vendor patches if available; if product is end-of-life, migrate to supported solution or implement WAF rules to filter/validate redirect parameters in HTTP requests.
- 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-2007-5437 — 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-2007-5437 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