# CVE-2019-16755: Deserialization in n/a

> Remote attackers can execute arbitrary commands on the operating system via pre-authenticated deserialization flaws in BMC Remedy ITSM Suite components.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cq5h-qx7v-mjg5

## What is CVE-2019-16755?

CVE-2019-16755 is a critical unsafe deserialization vulnerability in n/a, published on 26 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BMC 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2019-16755?

It affects 1 product.


Products: Bmc Myit Digital Workplace.

## How do I fix CVE-2019-16755?

No fix has been published for CVE-2019-16755 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-16755 being exploited?

There is no known exploitation of CVE-2019-16755 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16755 and fix it if it is affected.

What it is: CVE-2019-16755 is a critical unsafe deserialization vulnerability in n/a, published on 26 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16755 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-16755/ (Markdown: https://insights.sbomify.com/CVE-2019-16755/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-16755
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-16755
- OSV: https://osv.dev/vulnerability/CVE-2019-16755

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-16755/
Summaries are generated and may contain mistakes; the official description above is the record.