CVE-2007-0330
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 · uneditedBuffer overflow in wsbho2k0.dll, as used by wsftpurl.exe, in Ipswitch WS_FTP 2007 Professional allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a long ftp:// URL in an HTML document, and possibly other vectors.
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 confidenceBuffer overflow vulnerability in wsbho2k0.dll (used by wsftpurl.exe) in Ipswitch WS_FTP 2007 Professional allows remote attackers to cause denial of service and potentially execute arbitrary code via a specially crafted long ftp:// URL embedded in an HTML document.
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= 2007CVSS 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.
-
Verify WS_FTP 2007 Professional installationCheck Add/Remove Programs or look for WS_FTP Professional installation directory (typically C:\Program Files\Ipswitch\WS_FTP). Check the version information of wsftp.exe or the installer.Affected if WS_FTP Professional version 2007 is installed
-
Locate vulnerable wsbho2k0.dllSearch for wsbho2k0.dll in the WS_FTP installation directory (commonly in the Support\BHO or bin subfolder). Use Windows Explorer search or command: dir /s C:\*wsbho2k0.dllAffected if File wsbho2k0.dll exists in the WS_FTP installation folder
-
Confirm wsftpurl.exe is presentSearch for wsftpurl.exe in the WS_FTP installation directory or system. Use command: dir /s C:\*wsftpurl.exeAffected if wsftpurl.exe exists on the system
-
Check if BHO is registered in Internet ExplorerOpen Internet Explorer, go to Tools > Manage Add-ons. Look for 'WS_FTP URL' or 'wsftpurl' add-on under Browser Helper Objects. Alternatively, check registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects for entries containing wsftp or wsbhoAffected if WS_FTP Browser Helper Object is enabled in Internet Explorer
-
Verify file version of vulnerable DLLRight-click wsbho2k0.dll > Properties > Details to view file version. Compare against known affected version 2007.Affected if File version corresponds to WS_FTP 2007 Professional
A user is affected if WS_FTP 2007 Professional is installed, the wsbho2k0.dll and wsftpurl.exe files exist, and the Browser Helper Object is enabled in the browser.
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 patch from Ipswitch if available; alternatively, disable the wsftpurl.exe BHO add-on in affected browsers and warn users not to open untrusted HTML files containing FTP URLs.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0330 — 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-0330 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