CVE-2016-0365
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, when agent-relay Codestation artifact caching is enabled, allows remote attackers to bypass authentication and obtain sensitive artifact information via unspecified 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 · high confidenceIBM UrbanCode Deploy contains an authentication bypass vulnerability when agent-relay Codestation artifact caching is enabled. Remote attackers can bypass authentication mechanisms and obtain sensitive artifact information without proper credentials. The vulnerability affects versions 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.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/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 installed IBM UrbanCode Deploy versionLocate the product's version file or use the product's CLI tool to query the current version (for example, by inspecting installation directories or running version queries specific to the product)Affected if The installed version falls within 6.0.x before 6.0.1.13, 6.1.x before 6.1.3.3, or 6.2.x before 6.2.1.1
-
Determine if agent-relay component is configuredInspect the IBM UrbanCode Deploy configuration files or deployment topology to confirm whether any agent-relay components are installed and active in the environmentAffected if Agent-relay is present in the deployment configuration
-
Verify if Codestation artifact caching is enabledExamine the agent-relay configuration settings to determine whether the Codestation artifact caching feature is turned on (this is typically a configuration parameter or checkbox within the agent-relay settings)Affected if Codestation artifact caching is explicitly enabled on the agent-relay component
-
Confirm artifact endpoint accessibilityTest access to the Codestation artifact download endpoints without providing credentials to verify whether unauthenticated access is possibleAffected if Artifact endpoints respond without requiring authentication
You are affected if your IBM UrbanCode Deploy version is 6.0.x before 6.0.1.13, 6.1.x before 6.1.3.3, or 6.2.x before 6.2.1.1 AND the agent-relay Codestation artifact caching feature is enabled.
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 dataUpgrade to IBM UrbanCode Deploy versions 6.0.1.13, 6.1.3.3, 6.2.1.1 or later. Alternatively, if upgrading is not immediately feasible, disable the agent-relay Codestation artifact caching feature as a compensating control.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0365 — 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-0365 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