CVE-2016-15019: A vulnerability was found in tombh jekbox

Q: How do I fix CVE-2016-15019?

jekbox: upgrade to 2016-02-01. Exact commands for each OS are on this page.

Q: Is CVE-2016-15019 being exploited?

CVE-2016-15019 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-15019 affect?

CVE-2016-15019 affects jekbox. Severity is medium (CVSS 4.3). 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 b

Q: How urgent is CVE-2016-15019?

Priority 29/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2016-15019 is a medium-severity flaw (CVSS 4.3) affecting jekbox. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 44%)
CISA exploited list	No
Weakness	CWE-548, CWE-22
Published	2023-01-15
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: jekbox project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-01-15 19:15 UTCPublished CVE record published
2026-06-17 00:41 UTCUpdated Record last modified

jekbox project jekbox UPGRADE

Affected: < 2016-02-01

Fixed in: 2016-02-01

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jekbox || rpm -q jekbox || jekbox --version

2. UPGRADE to 2016-02-01 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jekbox

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jekbox

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-15019?

jekbox: upgrade to 2016-02-01. Exact commands for each OS are on this page.

Is CVE-2016-15019 being exploited?

CVE-2016-15019 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-15019 affect?

CVE-2016-15019 affects jekbox. Severity is medium (CVSS 4.3). 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 b

How urgent is CVE-2016-15019?

Priority 29/100. No elevated risk signals yet.

References

← Back to latest CVEs