CVE-2015-5018
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 Security Access Manager for Web 7.0.0 before FP19 and 8.0 before 8.0.1.3 IF3, and Security Access Manager 9.0 before 9.0.0.0 IF1, allows remote authenticated users to execute arbitrary OS commands by leveraging Local Management Interface (LMI) access.
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 confidenceCommand injection vulnerability in IBM Security Access Manager's Local Management Interface (LMI) allows authenticated remote users to execute arbitrary operating system commands by injecting them through LMI interfaces.
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= 9.0.0= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.0.4= 7.0.0.5= 7.0.0.6= 7.0.0.7= 7.0.0.8= 7.0.0.9= 7.0.0.10= 7.0.0.11= 7.0.0.12= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.5= 8.0.1= 8.0.1.0= 8.0.1.2= 8.0.1.3CVSS 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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
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 ISAM product and versionCheck the product's about page, version file, or run 'ibmsecadm' command-line tool with version query. Common locations: /opt/IBM/SAMAppliance/bin/ or check the firmware version through the appliance console.Affected if The installed version matches 9.0.0, 7.0.0.1-7.0.0.12, or 8.0.0.1/8.0.0.2/8.0.0.3/8.0.0.5/8.0.1/8.0.1.0/8.0.1.2/8.0.1.3
-
Verify the Local Management Interface (LMI) is enabledAccess the appliance admin console or check configuration files under /var/iseries/LMI or /opt/IBM/SAMAppliance/config/ for LMI settings. Look for 'LMI' or 'LocalManagementInterface' configuration entries.Affected if LMI is enabled and accessible on the appliance
-
Confirm LMI is exposed to network accessReview network configuration to determine if LMI listens on external/network interfaces. Check firewall rules and access control lists that permit LMI access from non-localhost addresses.Affected if LMI is bound to non-loopback interfaces or accessible from remote networks
-
Check LMI authentication configurationReview LMI user accounts and authentication settings. Determine whether user accounts with LMI access exist and whether they are accessible remotely.Affected if Remote authenticated users can access LMI interfaces
The environment is affected if IBM Security Access Manager or ISAM for Web is running an affected firmware version (9.0.0, 7.0.0.1-7.0.0.12, or 8.0.0.1/8.0.0.2/8.0.0.3/8.0.0.5/8.0.1/8.0.1.0/8.0.1.2/8.0.1.3) and the Local Management Interface is enabled and accessible to remote authenticated users.
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 vendor-supplied Interim Fixes (IF) or Fix Packs (FP): FP19 for version 7.0.0, IF3 for 8.0.1.3, and IF1 for 9.0.0.0. Restrict LMI access to only trusted administrative users.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5018 — 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-2015-5018 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