dbcve.org
Unified Endpoint ManagerApplication · Blackberry

CVE-2017-17442

MEDIUM · 6.1 CVSS v3.0 Published 2018-03-13
Fix available
A fix is available. Upgrade to after 12.7.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
In BlackBerry UEM Management Console version 12.7.1 and earlier, a reflected cross-site scripting vulnerability that could allow an attacker to execute script commands in the context of the affected UEM Management Console account by crafting a malicious link and then persuading a user with legitimate access to the Management Console to click on the malicious link.

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 confidence

A reflected cross-site scripting (XSS) vulnerability in BlackBerry UEM Management Console versions 12.7.1 and earlier allows attackers to inject malicious scripts via crafted URLs. When a legitimate user clicks the malicious link, the script executes in the context of their authenticated session, potentially enabling session hijacking or actions on behalf of the user.

MitigationApply vendor patch for BlackBerry UEM Management Console 12.7.1 and earlier. Until patched, users should avoid clicking untrusted links. Implement Content Security Policy (CSP) headers as an additional defense-in-depth measure.

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
Unified Endpoint ManagerApplication
Affected:<= 12.7.1

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm BlackBerry UEM Management Console is installed
    Check for BlackBerry UEM in your environment by reviewing installed software on servers or checking for the management console web service (typically on ports 8443 or 443). Query your asset inventory or CMDB for 'BlackBerry UEM' or 'BlackBerry Unified Endpoint Manager'.
    Affected if The product is not present in your environment, you are not affected by this vulnerability.
  2. Identify the BlackBerry UEM version
    Log into the BlackBerry UEM Management Console as an administrator. The version is typically displayed on the login page, in the footer of the console, or in the 'Settings > About' section. Alternatively, check release notes or installation documentation on the server where UEM is hosted.
    Affected if You cannot determine the version, treat the environment as potentially affected.
  3. Compare installed version against affected range
    If the version is 12.7.1 or earlier, the environment falls within the affected range. Versions greater than 12.7.1 are not affected by this specific CVE. Note that version numbering may include additional digits (e.g., 12.7.0, 12.6.x).
    Affected if Version is 12.7.1 or any version lower than 12.7.1 - the environment is affected by this vulnerability.
  4. Assess exposure of the Management Console web interface
    Determine if the BlackBerry UEM Management Console is accessible over the network. Check firewall rules, reverse proxy configurations, and VPN requirements. Identify whether internal or external users can reach the console URL.
    Affected if The console is not network-accessible (completely isolated), the attack surface is significantly reduced, though the vulnerability still exists in the software version.

Your environment is affected if BlackBerry UEM Management Console version 12.7.1 or earlier is installed and the web console interface is network-accessible to potential attackers who could deliver crafted malicious URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 12.7.1
Interim mitigation

Apply vendor patch for BlackBerry UEM Management Console 12.7.1 and earlier. Until patched, users should avoid clicking untrusted links. Implement Content Security Policy (CSP) headers as an additional defense-in-depth measure.

Fix this in Unified Endpoint Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17442 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-17442 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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