# CVE-2020-6856: XML external entity in n/a

> Attackers can read server files via XML External Entity injection in SOS JobScheduler JOC Cockpit run-time settings.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 6 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p9v4-8pgw-x8xr

## What is CVE-2020-6856?

CVE-2020-6856 is a medium-severity vulnerability in n/a, published on 6 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An XML External Entity (XEE) vulnerability exists in the JOC Cockpit component of SOS JobScheduler 1.12 and 1.13.2 allows attackers to read files from the server via an entity declaration in any of the XML documents that are used to specify the run-time settings of jobs and orders.

Weakness: CWE-776 (Improper Restriction of Recursive Entity References in DTDs)

## Which versions are affected by CVE-2020-6856?

It affects 1 product.


Products: Sos-Berlin Jobscheduler.

## How do I fix CVE-2020-6856?

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

## Is CVE-2020-6856 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12712](https://insights.sbomify.com/CVE-2020-12712/): Weak cryptography in n/a (high 7.5)
- [CVE-2020-6855](https://insights.sbomify.com/CVE-2020-6855/): Denial of service in n/a (medium 6.5)
- [CVE-2023-37272](https://insights.sbomify.com/CVE-2023-37272/): XSS vulnerability in JOC Cockpit branch 1.13 (medium 6.3)
- [CVE-2020-6854](https://insights.sbomify.com/CVE-2020-6854/): Cross-site Scripting in SOS JobScheduler (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6856 and fix it if it is affected.

What it is: CVE-2020-6856 is a medium-severity vulnerability in n/a, published on 6 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6856 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-2020-6856/ (Markdown: https://insights.sbomify.com/CVE-2020-6856/index.md)
```

## Sources

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

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