CVE-2013-5465
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 · uneditedIBM Maximo Asset Management 7.x before 7.1.1.7 LAFIX.20140319-0837, 7.1.1.11 before IFIX.20140323-0749, 7.1.1.12 before IFIX.20140321-1336, 7.5.x before 7.5.0.3 IFIX027, and 7.5.0.4 before IFIX011; SmartCloud Control Desk 7.x before 7.5.0.3 and 7.5.1.x before 7.5.1.2; and Tivoli IT Asset Management for IT, Tivoli Service Request Manager, Maximo Service Desk, and Change and Configuration Management Database (CCMDB) 7.x before 7.1.1.7 LAFIX.20140319-0837, 7.1.1.11 before IFIX.20140207-1801, and 7.1.1.12 before IFIX.20140218-1510 do not properly restrict file types during uploads, which allows remote authenticated users to have an unspecified impact via an invalid type.
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 confidenceThis is an insecure file upload vulnerability in IBM Maximo Asset Management and related products. The application fails to properly validate or restrict file types during upload operations, allowing authenticated users to upload files with potentially dangerous types (e.g., executable scripts, malicious code) that could lead to remote code execution or other unspecified impacts.
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= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.0.3= 7.5.0.4= 7.1= 7.1.1= 7.1.1.1= 7.1.1.2= 7.1.1.5= 7.1.1.6= 7.1.1.7= 7.1.1.7= 7.1.1.11= 7.1.1.12= 7.1.1.7= 7.1.1.11= 7.1.1.12= 7.0= 7.1= 7.1.1.7= 7.1.1.11= 7.1.1.12= 7.1.1= 7.1.1.7= 7.1.1.11= 7.1.1.12= 7.0= 7.5= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.1.0= 7.5.1.1CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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.
-
Identify installed product and versionLocate the installation directory and check version files (typically in the maximo/applications/maximo directory or via the Maximo About dialog in the web interface). Common files: MAXIMO.ear/maximo.jar/META-INF/manifest.mf or check the maximo.properties file.Affected if The installed version matches one of the affected versions listed: Maximo Asset Management 7.5.0.0-7.5.0.4 or 7.1.x; Change and Configuration Management Database 7.1.1.7, 7.1.1.11, 7.1.1.12; Maximo Service Desk 7.1.1.7, 7.1.1.11, 7.1.1.12; Tivoli Asset Management for IT 7.0, 7.1; Tivoli IT Asset Man
-
Verify file upload functionality is accessibleLog into the Maximo web interface as an authenticated user and navigate to document management or attachment upload features (typically under Go To > Documents or within asset/work order attachment sections). Confirm the upload endpoint is reachable.Affected if The file upload functionality is accessible to authenticated users in the application.
-
Inspect upload directory configuration and placementCheck the web application configuration (web.xml) and file storage paths in maximo.properties. Identify where uploaded files are stored and whether these directories are accessible via the web server.Affected if Uploaded files are stored within the webroot or in directories accessible via HTTP/HTTPS without restrictions.
-
Review uploaded files for dangerous typesExamine the document storage directory for files with executable extensions such as .jsp, .asp, .php, .exe, .bat, .sh, .jar, .class, or other scriptable file types. Check file creation timestamps and ownership.Affected if Files with executable or scriptable extensions exist in upload directories, especially if they were uploaded after the software was deployed.
A defender is affected if the installed IBM product version matches one of the listed affected versions AND the file upload feature is accessible to authenticated users, particularly if uploaded files are stored in web-accessible locations.
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 type validation using both extension whitelist filtering and magic byte/content-type verification. Store uploaded files outside the webroot and disable script execution in upload directories. Apply the vendor-supplied ifixes referenced in the advisory.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5465 — 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-5465 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