CVE-2017-17533: default.tcl in Tkabber 1.1 does not validate strings before launching the program specified by the BROWSER env

This month

HIGH 8.8DOWNGRADE

CVE-2017-17533 is a high-severity flaw (CVSS 8.8) affecting tkabber. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

default.tcl in Tkabber 1.1 does not validate strings before launching the program specified by the BROWSER environment variable, which might allow remote attackers to conduct argument-injection attacks via a crafted URL. NOTE: a third party has indicated that the attack cannot occur because of the argument-parsing behavior of the Tcl exec function

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Weakness	CWE-74
Published	2017-12-14
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: tkabber project

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

Am I affected?

Timeline

2017-12-14 16:29 UTCPublished CVE record published
2026-06-17 01:11 UTCUpdated Record last modified

tkabber project tkabber DOWNGRADE

Affected: 1.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.1

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 1.1 (Debian / Ubuntu)

apt-cache madison tkabber sudo apt install tkabber=<VERSION_BEFORE_1.1> sudo apt-mark hold tkabber

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list tkabber sudo dnf downgrade tkabber-<VERSION_BEFORE_1.1> sudo dnf versionlock add tkabber

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2017-17533?

tkabber: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-17533 being exploited?

CVE-2017-17533 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-2017-17533 affect?

CVE-2017-17533 affects tkabber. Severity is high (CVSS 8.8). default.tcl in Tkabber 1.1 does not validate strings before launching the program specified by the BROWSER environment variable, which might allow remote attackers to conduct argument-injection attacks via a crafted URL. NOTE: a third party

How urgent is CVE-2017-17533?

Priority 50/100. High severity

References

← Back to latest CVEs