CVE-2014-3073
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 · uneditedUnspecified vulnerability in IBM Security Access Manager (ISAM) for Mobile 8.0 and IBM Security Access Manager for Web 7.0 and 8.0 allows remote attackers to execute arbitrary code via unknown 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 · moderate confidenceCritical remote code execution vulnerability in IBM Security Access Manager for Mobile 8.0 and ISAM for Web 7.0/8.0. The vulnerability allows remote attackers to execute arbitrary code via unspecified vectors, indicating a severe input validation or authentication bypass flaw in the security appliance.
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= 8.0= 7.0= 8.0= 8.0= 7.0= 8.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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/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 installed ISAM product and versionRun 'lsitclis' or check the appliance/system information page for the exact version number of IBM Security Access Manager. For software installations, check the installed packages or program files for version 7.0, 8.0, or 8.0.0.Affected if The installed version matches exactly 7.0 or 8.0 for ISAM for Web, or exactly 8.0 for ISAM for Mobile.
-
Determine if running Software or Appliance variantIdentify whether the deployment is an Appliance (physical or virtual appliance) or Software installation. Check the product name: 'ISAM for Mobile Appliance', 'ISAM for Web Appliance', 'ISAM for Mobile Software', or 'ISAM for Web Software'.Affected if Running any of the four affected variants: ISAM for Mobile Software 8.0, ISAM for Web Software 7.0/8.0, ISAM for Mobile Appliance 8.0, or ISAM for Web Appliance 7.0/8.0.
-
Check if management interfaces are network-exposedReview firewall rules, network configurations, and access control lists to determine if the ISAM management interface (typically ports 443, 4443, or the admin console) is accessible from untrusted networks or the internet.Affected if Management interfaces are exposed to untrusted or public networks, increasing exploitability.
-
Inspect for unauthorized access or indicators of compromiseReview ISAM audit logs, access logs, and security event logs for unfamiliar admin accounts, unexpected configuration changes, or remote session activity from unknown IP addresses.Affected if Audit logs show unauthorized administrative actions, unexpected configuration modifications, or remote code execution indicators.
You are affected if you have IBM Security Access Manager for Mobile version 8.0 or ISAM for Web version 7.0 or 8.0 installed, regardless of whether it is software or appliance deployment.
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 IBM security patches for ISAM immediately; if patches unavailable, restrict network access to ISAM management interfaces and monitor for indicators of compromise. Consider disabling unneeded ISAM services until remediation is possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3073 — 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-2014-3073 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