# CVE-2023-37518: A code injection vulnerability affects HCL BigFix ServiceNow Data Flow

> A malicious authorized attacker can inject arbitrary code to execute within the running user's context in HCL BigFix ServiceNow Data Flow.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2024
- **Updated:** 29 May 2025
- **Also known as:** GHSA-j3rg-72x7-gm5r

## What is CVE-2023-37518?

CVE-2023-37518 is a medium-severity code injection vulnerability in HCL Software BigFix ServiceNow Data Flow, published on 30 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HCL BigFix ServiceNow is vulnerable to arbitrary code injection.  A malicious authorized attacker could inject arbitrary code and execute within the context of the running user.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-37518?

It affects 1 product.


Products: Hcltech Bigfix Servicenow Data Flow.

## How do I fix CVE-2023-37518?

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

## Is CVE-2023-37518 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-37518 and fix it if it is affected.

What it is: CVE-2023-37518 is a medium-severity code injection vulnerability in HCL Software BigFix ServiceNow Data Flow, published on 30 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-37518 in the wild and no public exploit code.

Affected product: HCL Software BigFix ServiceNow Data Flow. 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-2023-37518/ (Markdown: https://insights.sbomify.com/CVE-2023-37518/index.md)
```

## Sources

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

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