CVE-2006-6994
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 · uneditedUnrestricted file upload vulnerability in add.asp in OzzyWork Gallery, possibly 2.0 and earlier, allows remote attackers to upload and execute arbitrary ASP files by removing the client-side security checks.
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 confidenceUnrestricted file upload vulnerability in add.asp of OzzyWork Gallery 2.0 and earlier allows remote attackers to bypass client-side security checks and upload malicious ASP files that can be executed on the server, leading to remote code execution.
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.0CVSS 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
- Partial
AV:N/AC:L/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 OzzyWork Gallery is installedSearch the web server for files named 'add.asp' or directories containing 'ozzywork', 'gallery', or 'galeri' in the path. Check for application fingerprints such as 'Ozzywork' or 'OzzyWork Gallery' in page titles or source code.Affected if The application is found and is version 2.0 or earlier, or the version cannot be determined but the software matches the name 'Ozzywork Galeri'.
-
Locate the vulnerable add.asp upload scriptNavigate to or enumerate the 'add.asp' file within the Gallery installation path. Common paths may include /admin/, /upload/, or the root gallery directory.Affected if The file add.asp exists and is accessible via HTTP/HTTPS without authentication or with low-privilege user access.
-
Verify unrestricted file upload is possibleAttempt to upload a test file with an .asp extension (or double extension like .asp;.jpg) through the add.asp form. Bypass any client-side JavaScript validation and send the request directly via a proxy or curl command.Affected if The server accepts and saves the uploaded .asp file without rejecting it based on extension, MIME type, or file content validation.
-
Check for executable ASP files in upload directoriesInspect the upload directory configured in add.asp (or common upload folders like /uploads/, /images/, /files/) for any .asp, .aspx, .cer, or other executable file extensions that were not intentionally placed there.Affected if Unexpected .asp or other executable script files are found in upload directories, indicating the vulnerability has been exploited.
A system is affected if OzzyWork Gallery version 2.0 or earlier is installed and the add.asp script accepts and stores files with executable extensions like .asp without proper server-side validation.
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 server-side file validation to verify file types, contents, and extensions before saving uploaded files; disable or restrict the vulnerable upload functionality until properly remediated.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6994 — 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-6994 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