CVE-2016-0267
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 UrbanCode Deploy 6.0.x before 6.0.1.13, 6.1.x before 6.1.3.3, and 6.2.x before 6.2.1.1 allows remote authenticated users to obtain sensitive cleartext secure-property information via (1) the server UI or (2) a database request.
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 UrbanCode Deploy stores secure properties (such as passwords, API keys, or other credentials) in a way that allows authenticated users to retrieve the cleartext values through either the web UI or direct database queries, exposing sensitive information that should be masked or encrypted.
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.0= 6.0.1.0= 6.0.1.1= 6.0.1.2= 6.0.1.3= 6.0.1.4= 6.0.1.5= 6.0.1.6= 6.0.1.7= 6.0.1.8= 6.0.1.9= 6.0.1.10CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Determine installed IBM UrbanCode Deploy versionCheck the version number of the IBM UrbanCode Deploy server. This is typically visible in the product UI header, or can be found in installation logs or the server's about page.Affected if The installed version is 6.0, 6.0.1.0, 6.0.1.1, 6.0.1.2, 6.0.1.3, 6.0.1.4, 6.0.1.5, 6.0.1.6, 6.0.1.7, 6.0.1.8, 6.0.1.9, or 6.0.1.10.
-
Identify use of secure propertiesReview the IBM UrbanCode Deploy configurations and resource templates for any properties marked as secure, encrypted, or containing sensitive values such as passwords, API keys, or tokens.Affected if Secure properties are defined in the deployment configuration and the version is within the affected range.
-
Verify web UI displays of secure propertiesAs an authenticated user, navigate to resource or component property views in the web UI and observe whether any properties marked as secure are displayed in cleartext rather than masked.Affected if Secure properties appear as readable text in the web interface instead of being masked with dots or asterisks.
-
Inspect database for unmasked property valuesQuery the IBM UrbanCode Deploy database (if direct access is available) for secure property values. Look in tables related to properties or resources and check if sensitive data is stored in plaintext.Affected if The database contains unmasked or plaintext values for properties that should be encrypted or masked.
The environment is affected if the installed IBM UrbanCode Deploy version falls within 6.0 through 6.0.1.10 and secure properties are present and visible in plaintext through the UI or database queries.
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 vendor patches: upgrade to version 6.0.1.13, 6.1.3.3, or 6.2.1.1 (or later) which fix the insecure storage/display of secure properties. Audit affected systems for exposed credentials and rotate any compromised secrets.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0267 — 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-0267 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