# CVE-2018-19793: Command injection in n/a

> Remote attackers can execute arbitrary commands on jiacrontab servers by manipulating task editing parameters, leading to full system compromise.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8wph-c5mw-r2w4

## What is CVE-2018-19793?

CVE-2018-19793 is a high-severity command injection vulnerability in n/a, published on 3 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

jiacrontab 1.4.5 allows remote attackers to execute arbitrary commands via the crontab/task/edit?addr=localhost%3a20001 command and args parameters, as demonstrated by command=cat&args=/etc/passwd in the POST data.

## Which versions are affected by CVE-2018-19793?

It affects 1 product.


Products: Jiacrontab Project Jiacrontab.

## How do I fix CVE-2018-19793?

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

## Is CVE-2018-19793 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19793 and fix it if it is affected.

What it is: CVE-2018-19793 is a high-severity command injection vulnerability in n/a, published on 3 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19793 in the wild and no public exploit code.

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

## Sources

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

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