# CVE-2014-5393: Path traversal in n/a

> Authenticated users with info permission can read arbitrary files in the webroot via directory traversal in SOS JobScheduler.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/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:** 11 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v723-8xx7-26gh

## What is CVE-2014-5393?

CVE-2014-5393 is a medium-severity path traversal vulnerability in n/a, published on 11 Sep 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the JobScheduler Operations Center (JOC) in SOS JobScheduler before 1.6.4246 and 1.7.x before 1.7.4241 allows remote authenticated users with the info permission to read arbitrary files in the webroot via unspecified vectors.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2014-5393?

It affects 1 product.


Products: Sos Jobscheduler.

## How do I fix CVE-2014-5393?

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

## Is CVE-2014-5393 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5392](https://insights.sbomify.com/CVE-2014-5392/): XML external entity in n/a (medium 5.8)
- [CVE-2014-5391](https://insights.sbomify.com/CVE-2014-5391/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-5393 and fix it if it is affected.

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

## Sources

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

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