# CVE-2016-15019: tombh jekbox server.rb exposure of information through directory listing

> Remote attackers can access sensitive information via directory listing in the jekbox server component.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 15 Jan 2023
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-f28r-c98m-qr3r

## What is CVE-2016-15019?

CVE-2016-15019 is a medium-severity vulnerability in tombh jekbox, published on 15 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in tombh jekbox. It has been rated as problematic. This issue affects some unknown processing of the file lib/server.rb. The manipulation leads to exposure of information through directory listing. The attack may be initiated remotely. The patch is named 64eb2677671018fc08b96718b81e3dbc83693190. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218375.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-548 (Exposure of Information Through Directory Listing)

## Which versions are affected by CVE-2016-15019?

It affects 1 product.


Products: Jekbox Project Jekbox.

## How do I fix CVE-2016-15019?

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

## Is CVE-2016-15019 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15019 and fix it if it is affected.

What it is: CVE-2016-15019 is a medium-severity vulnerability in tombh jekbox, published on 15 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-15019 in the wild and no public exploit code.

Affected product: tombh jekbox. 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-2016-15019/ (Markdown: https://insights.sbomify.com/CVE-2016-15019/index.md)
```

## Sources

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

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