# CVE-2019-19230: Deserialization in CA Release Automation

> Remote attackers can execute arbitrary code via unsafe deserialization in the DataManagement component of CA Release Automation.

- **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:** 9 Dec 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6w3p-7vr4-75hx

## What is CVE-2019-19230?

CVE-2019-19230 is a critical unsafe deserialization vulnerability in CA Release Automation, published on 9 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unsafe deserialization vulnerability exists in CA Release Automation (Nolio) 6.6 with the DataManagement component that can allow a remote attacker to execute arbitrary code.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Broadcom Nolio.

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

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

## Is CVE-2019-19230 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19230 is a critical unsafe deserialization vulnerability in CA Release Automation, published on 9 Dec 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-19230 in the wild and no public exploit code.

Affected product: CA Release Automation. 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-19230/ (Markdown: https://insights.sbomify.com/CVE-2019-19230/index.md)
```

## Sources

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

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