CVE-2013-5464
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.x before 7.5.0.3 IFIX027, 7.5.0.4 before IFIX011, and 7.5.0.5 before IFIX006 and SmartCloud Control Desk 7.x before 7.5.0.3 and 7.5.1.x before 7.5.1.2 allow remote authenticated users to bypass intended access restrictions, and modify physical counts associated with restricted storerooms, via unspecified vectors.
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 confidenceAccess control bypass vulnerability in IBM Maximo Asset Management and SmartCloud Control Desk allows authenticated users to modify physical inventory counts in storerooms that should be restricted by access controls. The vulnerability exploits insufficient authorization checks in the storeroom management functionality.
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.5.0.5= 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 versionCheck the version of IBM Maximo Asset Management or SmartCloud Control Desk installed in your environment. In Maximo, this can typically be found in the System Configuration > Platform Configuration > System Properties or via the About dialog. For SmartCloud Control Desk, check the installation directory or version information in the administration console.Affected if The installed version matches one of the affected versions: Maximo Asset Management 7.5.0.0 through 7.5.0.5, or SmartCloud Control Desk 7.0, 7.5, 7.5.0.0, 7.5.0.1, 7.5.0.2, 7.5.1.0, or 7.5.1.1.
-
Confirm storeroom management is accessibleVerify that users have access to the Inventory module and storeroom management features. Navigate to Inventory > Storerooms or equivalent in the web interface to confirm the functionality exists and is accessible to authenticated users.Affected if Storeroom management functionality is available and users with standard inventory roles can access it.
-
Review access control configuration for storeroom modificationsExamine the security groups and permissions assigned to users who can modify inventory counts. Check the actions that are permitted on storeroom records, specifically the ability to update physical inventory counts. Review the security configuration in the Security Groups application.Affected if Users with non-administrative roles can modify inventory counts in storerooms that should be restricted based on your access control requirements.
-
Test unauthorized storeroom modification attemptAs a user with limited inventory permissions (not system administrator), attempt to modify the physical inventory count in a storeroom that should be restricted based on your access control configuration. Document whether the modification succeeds when it should be blocked.Affected if A user without explicit storeroom modification rights is able to successfully change inventory counts in a restricted storeroom.
You are affected if your environment runs an affected version of IBM Maximo Asset Management or SmartCloud Control Desk AND users with restricted access can modify inventory counts in storerooms that should be protected by access controls.
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 appropriate IBM IFIX patches: IFIX027 for version 7.5.0.3, IFIX011 for 7.5.0.4, IFIX006 for 7.5.0.5, or the equivalent patches for SmartCloud Control Desk (7.5.0.3 or 7.5.1.2). After patching, verify that access controls properly restrict storeroom modifications.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5464 — 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-5464 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