CVE-2016-5967
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 · uneditedThe installation component in IBM Rational Asset Analyzer (RAA) 6.1.0 before FP10 allows local users to discover the WAS Admin password by reading IM native logs.
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 confidenceThe installation component in IBM Rational Asset Analyzer (RAA) 6.1.0 before FP10 writes the WebSphere Application Server (WAS) Admin password in plaintext to Installation Manager (IM) native log files during installation. Local users with access to these log files can read and obtain the WAS Admin credentials.
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= 6.1.0= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.1.0.4= 6.1.0.5= 6.1.0.6= 6.1.0.7= 6.1.0.8= 6.1.0.9CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify IBM RAA installation and versionLocate the IBM Rational Asset Analyzer installation directory and check for version markers such as a version file, product.info, or registry entries. Common locations include the Installation Manager agent.data file or the RAA installation root directory.Affected if The installed version is 6.1.0 through 6.1.0.9 (any version before FP10)
-
Identify Installation Manager log file locationsCheck the Installation Manager log directories. These are typically found in the IM data directory, commonly under the user or system profile used during installation, such as var/ibm/InstallationManager/logs or similar native logging locations.Affected if Installation Manager log files exist from the RAA installation period
-
Search log files for plaintext credentialsExamine the Installation Manager native log files for the WebSphere Application Server Admin password. Search the log file contents for strings matching the WAS admin user ID or password patterns in plaintext. Use text search tools like grep, strings, or a text editor to inspect log file contents.Affected if The WAS Admin password appears in plaintext within the IM log files
-
Verify file permissions on log directoriesCheck file system permissions on the Installation Manager log directories. Determine if unprivileged local users have read access to the log files containing the plaintext password.Affected if Log files are readable by users other than the administrator who performed the installation
The environment is affected if IBM RAA version 6.1.0.x (where x is 0-9) is installed AND the Installation Manager log files from installation contain the WAS Admin password in plaintext and are readable by unauthorized local 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 IBM RAA version 6.1.0 FP10 or later which addresses the insecure logging. Additionally, change the WAS Admin password if exposure is suspected, and restrict file permissions on IM log directories to limit access.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5967 — 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-2016-5967 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