CVE-2004-0060
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 · uneditedWWW File Share Pro 2.42 and earlier allows remote attackers to cause a denial of service (crash) via a large POST request.
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 confidenceWWW File Share Pro versions 2.42 and earlier contains a denial-of-service vulnerability where the application crashes when receiving a large HTTP POST request. The issue stems from insufficient bounds checking or input validation when handling POST data, allowing remote attackers to send oversized requests that cause the service to fail.
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.42CVSS 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
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Check if WWW File Share Pro is installedLook for the application on the system - check Program Files directory on Windows, or search for executable files named 'wwwfilesharepro.exe' or similar using file system searchAffected if The application is present on the system
-
Identify the installed version numberRight-click the executable file, select Properties, and check the Version tab. Alternatively, run the application and look for version information in the About or Help menuAffected if The version cannot be determined or is 2.42 or earlier
-
Verify the HTTP service is accessibleAttempt to connect to the server on the port where WWW File Share Pro is configured to run (typically port 80 or 8080). Use a browser or curl: curl -I http://target:port/Affected if The service is reachable and accepts HTTP connections
-
Confirm version is within affected rangeCompare your installed version number to the affected range: any version 2.42 or lower is vulnerableAffected if The installed version is 2.42 or any earlier version number
You are affected if WWW File Share Pro version 2.42 or earlier is installed and the HTTP service is running and accessible on the network.
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 WWW File Share Pro if available. If no update exists, implement request size limits at the web server level (e.g., LimitRequestBody directive in Apache) or deploy a web application firewall to block abnormally large POST requests.
- 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-2004-0060 — 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-2004-0060 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