# CVE-2019-19544: Privilege escalation in CA Automic Dollar Universe

> Local attackers can elevate privileges due to the uxdqmsrv binary being setuid root in CA Automic Dollar Universe.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8v3g-x8mx-3cwf

## What is CVE-2019-19544?

CVE-2019-19544 is a high-severity vulnerability in CA Automic Dollar Universe, published on 8 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CA Automic Dollar Universe 5.3.3 contains a vulnerability, related to the uxdqmsrv binary being setuid root, that allows local attackers to elevate privileges. This vulnerability was reported to CA several years after CA Automic Dollar Universe 5.3.3 reached End of Life (EOL) status on April 1, 2015.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Broadcom Ca Automic Dollar Universe.

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

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

## Is CVE-2019-19544 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19544 is a high-severity vulnerability in CA Automic Dollar Universe, published on 8 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19544 in the wild and no public exploit code.

Affected product: CA Automic Dollar Universe. 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-19544/ (Markdown: https://insights.sbomify.com/CVE-2019-19544/index.md)
```

## Sources

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

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