CVE-2017-1207
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 WebSphere Message Broker stores user credentials in plain in clear text which can be read by a local user. IBM X-Force ID: 123777.
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 confidenceIBM WebSphere Message Broker stores user credentials in plain text rather than using secure hashing or encryption. A local user with access to the system can read these unencrypted credentials from stored configuration or data files, potentially gaining unauthorized access to legitimate accounts.
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.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.4= 8.0.0.5= 8.0.0.6= 8.0.0.7= 9.0.0= 9.0.0.1= 9.0.0.2= 9.0.0.3= 9.0.0.4= 9.0.0.5= 9.0.0.6= 9.0.0.7= 10.0.0= 10.0.0.1= 10.0.0.2= 10.0.0.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
- 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.
-
Identify the installed product and versionRun 'mqsireportproperties' or check the product installation directory for version information. On Windows, check the installation path typically under C:\Program Files\IBM\IIB or C:\Program Files\IBM\WebSphere Message Broker. On Linux/Unix, check /opt/ibm/IIB or /opt/ibm/WMB.Affected if The installed version matches any of these: IBM WebSphere Message Broker 8.0.0.0-8.0.0.7, or IBM Integration Bus 9.0.0-9.0.0.7, or IBM Integration Bus 10.0.0-10.0.0.3
-
Locate configuration files that may contain user credentialsSearch the installation directory and working directories for configuration files such as bar files, override properties, userdefined elements, or any XML/properties files that may store authentication data.Affected if Configuration or data files exist in the environment that contain stored user credentials
-
Examine credential storage for encryptionOpen the identified configuration files and inspect whether the stored credentials appear as plain text or are encrypted/hashed. Look for readable password strings versus encoded or hashed values.Affected if Credentials are stored in plain text readable format rather than being encrypted or hashed
You are affected if you run any of the listed versions AND you find credentials stored in plain text within configuration or data files accessible on the system.
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 dataMigrate credentials to use strong encryption or salted hashing mechanisms supported by the platform. Review and rotate all affected credentials as a precautionary measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1207 — 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-1207 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