CVE-2006-2353
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 · uneditedNmConsole/DeviceSelection.asp in Ipswitch WhatsUp Professional 2006 and WhatsUp Professional 2006 Premium allows remote attackers to redirect users to other websites via the (1) sCancelURL and possibly (2) sRedirectUrl parameters.
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 confidenceNmConsole/DeviceSelection.asp in Ipswitch WhatsUp Professional 2006 does not validate the sCancelURL and sRedirectUrl parameters before using them in redirects, allowing attackers to craft malicious URLs that redirect users to external malicious sites. This is a classic open redirect vulnerability that can facilitate 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= 2006= 2006_premiumCVSS 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.
-
Identify installed WhatsUp Professional versionCheck the installed version of Ipswitch WhatsUp Professional on the system - look in Add/Remove Programs, the installation directory, or application documentation to confirm the exact version numberAffected if Version is exactly 2006 or 2006_premium (these are the only affected versions listed)
-
Locate the vulnerable NmConsole componentCheck if the NmConsole web application directory exists on the server - the vulnerable file is NmConsole/DeviceSelection.asp within the WhatsUp Professional web rootAffected if The NmConsole directory and DeviceSelection.asp file exist on the system
-
Determine if the web interface is accessibleVerify that the WhatsUp Professional web interface (typically on port 80/443 or configured web port) is accessible from network clientsAffected if The NmConsole web application is exposed and reachable over the network
-
Test for open redirect vulnerabilityIf the application is accessible, attempt a test request to DeviceSelection.asp with a malicious sRedirectUrl parameter (such as http://example.com) and observe if the application redirects to the external site without validationAffected if The application accepts external URLs in sRedirectUrl or sCancelURL parameters and performs a redirect without validating that the URL is internal
A system is affected if it runs WhatsUp Professional version 2006 or 2006_premium, has the NmConsole web component installed and accessible, and the redirect parameters are not validated before use in redirects.
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 dataImplement strict validation of redirect URL parameters to ensure they only point to internal resources (relative paths or trusted internal domains). Reject or sanitize any URLs containing external domains or suspicious patterns.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2353 — 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-2006-2353 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