# CVE-2023-39017: Code injection in n/a

> A code injection vulnerability in Quartz Jobs allows attackers to execute arbitrary code via unchecked arguments, though exploitation is disputed.

- **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:** 28 Jul 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9jc9-7p44-pm6c

## What is CVE-2023-39017?

CVE-2023-39017 is a critical code injection vulnerability in n/a, published on 28 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

quartz-jobs 2.3.2 and below was discovered to contain a code injection vulnerability in the component org.quartz.jobs.ee.jms.SendQueueMessageJob.execute. This vulnerability is exploited via passing an unchecked argument. NOTE: this is disputed by multiple parties because it is not plausible that untrusted user input would reach the code location where injection must occur.

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

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

It affects 1 product.


Products: Softwareag Quartz.

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

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

## Is CVE-2023-39017 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39017 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39017 is a critical code injection vulnerability in n/a, published on 28 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39017 exists.

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-2023-39017/ (Markdown: https://insights.sbomify.com/CVE-2023-39017/index.md)
```

## Sources

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

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