CVE-2020-28054: JamoDat TSMManager Collector version up to 6.5.0.21 is vulnerable to an Authorization Bypass because the Colle

Q: How do I fix CVE-2020-28054?

tsmmanager: upgrade to newer than 6.5.0.21. Exact commands for each OS are on this page.

Q: Is CVE-2020-28054 being exploited?

CVE-2020-28054 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-2020-28054 affect?

CVE-2020-28054 affects tsmmanager. Severity is high (CVSS 7.5). JamoDat TSMManager Collector version up to 6.5.0.21 is vulnerable to an Authorization Bypass because the Collector component is not properly validating an authenticated session with the Viewer. If the Viewer has been modified (binary patche

Q: How urgent is CVE-2020-28054?

Priority 51/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2020-28054 is a high-severity flaw (CVSS 7.5) affecting tsmmanager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

JamoDat TSMManager Collector version up to 6.5.0.21 is vulnerable to an Authorization Bypass because the Collector component is not properly validating an authenticated session with the Viewer. If the Viewer has been modified (binary patched) and the Bypass Login functionality is being used, an attacker can request every Collector's functionality as if they were a properly logged-in user: administrating connected instances, reviewing logs, editin

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.0% (top 19%)
CISA exploited list	No
Published	2020-11-19
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: tsmmanager

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

Am I affected?

Timeline

2020-11-19 16:15 UTCPublished CVE record published
2026-06-17 03:10 UTCUpdated Record last modified

tsmmanager tsmmanager UPGRADE

Affected: <= 6.5.0.21

Fixed in: newer than 6.5.0.21

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 6.5.0.21 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade tsmmanager

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-2020-28054?

tsmmanager: upgrade to newer than 6.5.0.21. Exact commands for each OS are on this page.

Is CVE-2020-28054 being exploited?

CVE-2020-28054 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-2020-28054 affect?

CVE-2020-28054 affects tsmmanager. Severity is high (CVSS 7.5). JamoDat TSMManager Collector version up to 6.5.0.21 is vulnerable to an Authorization Bypass because the Collector component is not properly validating an authenticated session with the Viewer. If the Viewer has been modified (binary patche

How urgent is CVE-2020-28054?

Priority 51/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs