CVE-2006-2357
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 · uneditedIpswitch WhatsUp Professional 2006 and WhatsUp Professional 2006 Premium allows remote attackers to obtain source code for scripts via a trailing dot in a request to NmConsole/Login.asp.
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 confidenceThis is a path traversal vulnerability in Ipswitch WhatsUp Professional 2006 where a trailing dot appended to the NmConsole/Login.asp request causes the web server to return the unprocessed source code instead of executing the ASP script. This allows remote attackers to view application source code, potentially revealing credentials, logic, or additional vulnerabilities.
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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 WhatsUp Professional installationCheck for Ipswitch WhatsUp Professional installation by looking in common locations: C:\Program Files\Ipswitch\WhatsUp Professional, or check Windows Services for WhatsUp Professional services, or examine IIS/Apache configuration for NmConsole virtual directoryAffected if Ipswitch WhatsUp Professional 2006 is installed and the NmConsole web directory exists
-
Confirm installed versionLocate version information in the installation directory, check the program properties, or query the Windows Registry under HKLM\SOFTWARE\Ipswitch\WhatsUp for the Version valueAffected if The installed version is exactly 2006 or 2006_premium
-
Identify NmConsole web endpointLocate the NmConsole directory in the web server root (typically under the web root of the WhatsUp Professional installation) and verify Login.asp existsAffected if The file NmConsole/Login.asp exists in the web directory
-
Test ASP processing behaviorUsing a local or authenticated HTTP request tool, send a request to NmConsole/Login.asp and observe whether the response contains processed ASP output (HTML/headers) or returns raw ASP source code with <% %> tags visibleAffected if Requesting NmConsole/Login.asp returns unprocessed ASP source code instead of executed output, or the trailing-dot variant (Login.asp.) returns source code
The environment is affected if Ipswitch WhatsUp Professional version 2006 or 2006_premium is installed with the NmConsole/Login.asp endpoint accessible and the web server fails to process ASP scripts (returning source code instead of executed output).
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 any available vendor patches for WhatsUp Professional 2006. If no patch exists, restrict or disable access to the NmConsole directory, or configure the web server to process all .asp files as scripts regardless of request syntax.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2357 — 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-2357 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