CVE-2017-1749
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.1 through 6.9.6.0 could allow a remote attacker to traverse directories on the system. An unauthenticated attacker could alter UCD deployments. IBM X-Force ID: 135522.
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 versions 6.1 through 6.9.6.0 contain a directory traversal vulnerability that allows unauthenticated remote attackers to traverse directories outside the intended web root and potentially alter UCD deployments. This is a classic path traversal flaw where input validation is insufficient.
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, <= 6.9.6.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 IBM UrbanCode Deploy versionLocate the version file in the installation directory. Common paths include: <install_dir>/server/etc/version.txt, <install_dir>/bin/version.properties, or check the welcome page of the web UI at /cli/version. Alternatively, check the server logs in <install_dir>/var/log for startup messages that display the version.Affected if The installed version falls within 6.1 through 6.9.6.0 inclusive
-
Confirm web application is runningVerify the IBM UrbanCode Deploy web application is accessible. Attempt to reach the login page at the standard UCD port (usually 8080 or 8443) via HTTP/HTTPS. Check if the server process is running and the web ear file is deployed.Affected if The web interface is exposed and accepts connections
-
Check for unauthenticated access to web resourcesTest whether the web root accepts requests without authentication. Attempt to access common endpoints such as /rest/api/ or /web/ without providing credentials. Review access logs for unauthenticated requests to path traversal patterns.Affected if Unauthenticated access to web endpoints is permitted
The environment is affected if IBM UrbanCode Deploy version 6.1 through 6.9.6.0 is installed and the web interface is network-accessible without authentication controls blocking traversal attempts.
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 IBM UrbanCode Deploy to version 6.9.6.1 or later which contains the fix for this vulnerability. If immediate patching is not possible, restrict network access to the UCD server and monitor for suspicious traversal patterns in HTTP requests.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1749 — 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-1749 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