CVE-2013-6332
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 IBM Algo One UDS 4.7.0 through 5.0.0 allows remote authenticated users to execute arbitrary code by uploading a .jsp file and then launching it.
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 IBM Algo One UDS versions 4.7.0 through 5.0.0 allows authenticated remote users to upload arbitrary .jsp files which are subsequently executable by the web server, enabling complete remote code execution on the underlying system.
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= 4.7.0= 4.7.1= 4.8.0= 4.9.0= 4.9.1= 5.0.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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/C:C/I:C/A:C
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 IBM Algo One UDS versionLocate the installed version of IBM Algo One UDS by checking the product documentation, installation directory, or version information file typically found in the application root or via the product's built-in version commandAffected if The installed version is 4.7.0, 4.7.1, 4.8.0, 4.9.0, 4.9.1, or 5.0.0
-
Confirm upload functionality is accessibleIdentify whether the file upload endpoint/module is enabled and exposed in the IBM Algo One UDS web interface by reviewing the application's exposed URLs or service endpointsAffected if The upload feature is enabled and accessible to authenticated users
-
Verify upload accepts executable extensionsTest or inspect the file upload mechanism to determine if .jsp file extensions are accepted, either by reviewing upload validation logic in the application configuration or by attempting a test upload with a benign .jsp fileAffected if The application accepts and stores files with .jsp extension without rejecting them based on file type validation
-
Check uploaded file storage locationExamine the application configuration to determine where uploaded files are stored relative to the web server document rootAffected if Uploaded files are stored within the webroot or in a directory that the web server can serve and execute
-
Verify script execution is not blocked in upload directoryInspect the web server configuration (such as Apache, IIS, or embedded server settings) to confirm whether script execution is disabled in the directory where uploads are storedAffected if The upload directory allows script execution (MIME types for .jsp are not blocked, or no execution prevention is configured)
The environment is affected if IBM Algo One UDS version 4.7.0 through 5.0.0 is running with the upload feature enabled, accepting .jsp files, and storing them in a location where the web server can execute them.
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 allowlist-based file type validation, reject files with executable extensions (.jsp, .jspx, .exe, .sh, etc.), store uploads outside webroot, disable script execution in upload directories, and enforce proper authentication/authorization for upload functionality.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6332 — 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-2013-6332 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