# CVE-2022-38661: HCL Workload Automation is affected by a vulnerability in Jlog component of the Master Domain Manager

> A local user can overwrite key system files in HCL Workload Automation, causing the system to crash.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2022
- **Updated:** 2 May 2025
- **Also known as:** GHSA-4vmw-g457-xcj2

## What is CVE-2022-38661?

CVE-2022-38661 is a medium-severity path traversal vulnerability in HCL Workload Automation, published on 4 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

HCL Workload Automation could allow a local user to overwrite key system files which would cause the system to crash.

## Which versions are affected by CVE-2022-38661?

It affects 1 product.


Products: Hcltechsw Hcl Workload Automation.

## How do I fix CVE-2022-38661?

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

## Is CVE-2022-38661 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38661 and fix it if it is affected.

What it is: CVE-2022-38661 is a medium-severity path traversal vulnerability in HCL Workload Automation, published on 4 Nov 2022. 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-2022-38661 in the wild and no public exploit code.

Affected product: HCL Workload 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-2022-38661/ (Markdown: https://insights.sbomify.com/CVE-2022-38661/index.md)
```

## Sources

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

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