# CVE-2022-4322: maku-boot Scheduled Task AbstractScheduleJob.java doExecute injection

> Remote attackers can exploit an injection flaw in the scheduled task handler to execute arbitrary code or access data.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 7 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-3qq9-74gh-x46m

## What is CVE-2022-4322?

CVE-2022-4322 is a medium-severity SQL injection vulnerability in unspecified maku-boot, published on 7 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in maku-boot up to 2.2.0. This affects the function doExecute of the file AbstractScheduleJob.java of the component Scheduled Task Handler. The manipulation leads to injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 446eb7294332efca2bfd791bc37281cedac0d0ff. It is recommended to apply a patch to fix this issue. The identifier VDB-215013 was assigned to this vulnerability.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-707 (Improper Neutralization)

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

It affects 1 product.


Products: Maku Maku-Boot.

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

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

## Is CVE-2022-4322 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4322 is a medium-severity SQL injection vulnerability in unspecified maku-boot, published on 7 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4322 exists.

Affected product: unspecified maku-boot. 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-4322/ (Markdown: https://insights.sbomify.com/CVE-2022-4322/index.md)
```

## Sources

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

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