CVE-2017-20123: A vulnerability was found in Viscosity 1.6.7

This month

HIGH 8.8DOWNGRADE

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

A vulnerability was found in Viscosity 1.6.7. It has been classified as critical. This affects an unknown part of the component DLL Handler. The manipulation leads to untrusted search path. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.6.8 is able to address this issue. It is recommended to upgrade the affected component.

Why this priority

High severity
Public exploit reference

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	Low
User interaction	None
EPSS exploit chance	1.3% (top 30%)
CISA exploited list	No
Weakness	CWE-426, CWE-427
Published	2022-06-30
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: sparklabs

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

Am I affected?

Timeline

2022-06-30 05:15 UTCPublished CVE record published
2026-06-17 01:15 UTCUpdated Record last modified

sparklabs viscosity DOWNGRADE

Affected: 1.6.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.6.7

1. Check installed version

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

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

apt-cache madison viscosity sudo apt install viscosity=<VERSION_BEFORE_1.6.7> sudo apt-mark hold viscosity

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

dnf --showduplicates list viscosity sudo dnf downgrade viscosity-<VERSION_BEFORE_1.6.7> sudo dnf versionlock add viscosity

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-20123?

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

Is CVE-2017-20123 being exploited?

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

CVE-2017-20123 affects viscosity. Severity is high (CVSS 8.8). A vulnerability was found in Viscosity 1.6.7. It has been classified as critical. This affects an unknown part of the component DLL Handler. The manipulation leads to untrusted search path. It is possible to initiate the attack remotely. Th

How urgent is CVE-2017-20123?

Priority 53/100. High severity; Public exploit reference

References

← Back to latest CVEs