CVE-2017-1352
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.5 and 7.6 could allow an authenticated user to inject commands into work orders that could be executed by another user that downloads the affected file. IBM X-Force ID: 126538.
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 confidenceIBM Maximo Asset Management 7.5 and 7.6 contains a command injection vulnerability where an authenticated user can embed malicious commands into work order data. When another user downloads the affected work order file, the injected commands execute on the victim's system. This is a classic file-based command injection requiring user interaction (victim must download the file).
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= 7.6CVSS 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
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
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 the installed Maximo Asset Management versionLocate the version of IBM Maximo Asset Management installed in your environment. This can typically be found in the About dialog within the Maximo application, in the System Information console, or by running version lookup commands such as mxconfig or checking the installation logs. Confirm whether the version is exactly 7.5 or exactly 7.6.Affected if The installed version is 7.5 or 7.6 (exact match)
-
Confirm user authentication is enabledVerify that the Maximo user authentication system is active and users can log in. Check the security configuration settings and confirm that standard user accounts have access to the system. The vulnerability requires an authenticated user to inject malicious commands into work order data.Affected if Standard users can authenticate to the Maximo system
-
Determine if work order download functionality is accessibleCheck whether the work order attachment download feature is enabled in Maximo. This is configured through the Application Designer, security groups, or system configuration menus. Verify if users have permission to download work order files and attachments.Affected if Users have permission to download work order files or attachments
If your environment runs Maximo Asset Management version 7.5 or 7.6 with active user authentication and enabled work order download functionality, you are affected by CVE-2017-1352.
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 the IBM fix for this vulnerability (contact IBM for interim security patch or upgrade to a patched version). Until patched, restrict download functionality for work order attachments or implement additional file-type validation and content inspection at the perimeter.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1352 — 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-2017-1352 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