CVE-2019-16755
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 · uneditedBMC Remedy ITSM Suite is prone to unspecified vulnerabilities in both DWP and SmartIT components, which can permit remote attackers to perform pre-authenticated remote commands execution on the Operating System running the targeted application. Affected DWP versions: versions: 3.x to 18.x, all versions, service packs, and patches are affected by this vulnerability. Affected SmartIT versions: 1.x, 2.0, 18.05, 18.08, and 19.02, all versions, service packs, and patches are affected by this vulnerability.
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 confidenceBMC Remedy ITSM Suite contains pre-authenticated remote command execution vulnerabilities in both DWP (versions 3.x-18.x) and SmartIT (versions 1.x, 2.0, 18.05, 18.08, 19.02) components, allowing unauthenticated attackers to execute arbitrary operating system commands on servers running the affected application.
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< 18.08.00CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 if BMC MyIT Digital Workplace is installedCheck for the application in standard installation paths such as C:\Program Files\BMC Software\MyIT or /opt/bmc/myit, or look for the BMC MyIT service in Windows Services or Linux service listingsAffected if BMC MyIT Digital Workplace is installed on the system
-
Check the installed version of BMC MyIT Digital WorkplaceLook for version information in the installation directory, typically in a version.txt, about.html, or in the application's help/about section. On Windows, also check the Windows Registry under HKLM\SOFTWARE\BMC Software\MyIT for the Version valueAffected if The installed version is lower than 18.08.00 (any version in the 3.x-18.x range)
-
Identify if DWP (Digital Workplace) component is runningCheck for the DWP service process, typically named dwp.exe on Windows or dwpd on Linux, listening on ports commonly used by DWP (usually port 8080 or 8443). Use 'netstat -an | findstr 8080' or 'netstat -an | grep -E "(8080|8443)"' to identify listening portsAffected if DWP service is running and listening on network ports
-
Identify if SmartIT component is runningCheck for the SmartIT service process or look for the SmartIT application server running, typically on ports 8080, 8443, or 8000. Review the BMC Remedy AR System server configuration for SmartIT deploymentAffected if SmartIT component is deployed and running on the server
-
Verify network exposure of the affected serviceReview firewall rules and network configuration to determine if the DWP or SmartIT web interfaces are accessible from untrusted networks. Use 'nmap -p 8080,8443 <target>' or review inbound firewall rules for the server IPAffected if The DWP or SmartIT web interface is accessible from external/untrusted networks without authentication
A system is affected if BMC MyIT Digital Workplace version is below 18.08.00 AND the DWP or SmartIT web component is running and network-accessible, allowing unauthenticated remote command execution.
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 data18.08.00
Apply vendor-provided patches immediately; if no patch exists, implement network segmentation, restrict external access to affected services, and deploy WAF/IPS controls as compensating measures.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16755 — 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-2019-16755 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