CVE-2017-20039: A vulnerability was found in SICUNET Access Controller 0.32-05z

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2017-20039 is a critical-severity flaw (CVSS 9.8) affecting access control. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in SICUNET Access Controller 0.32-05z. It has been classified as very critical. This affects an unknown part. The manipulation leads to weak authentication. It is possible to initiate the attack remotely.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

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

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.3% (top 31%)
CISA exploited list	No
Weakness	CWE-259, CWE-798
Published	2022-06-11
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: sicunet

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

Am I affected?

Timeline

2022-06-11 10:15 UTCPublished CVE record published
2026-06-17 01:14 UTCUpdated Record last modified

sicunet access control DOWNGRADE

Affected: 0.32-05z

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.32-05z

1. Check installed version

apt-cache policy access-control || rpm -q access-control || access-control --version

2. No fixed release: DOWNGRADE to a release before 0.32-05z (Debian / Ubuntu)

apt-cache madison access-control sudo apt install access-control=<VERSION_BEFORE_0.32-05z> sudo apt-mark hold access-control

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

dnf --showduplicates list access-control sudo dnf downgrade access-control-<VERSION_BEFORE_0.32-05z> sudo dnf versionlock add access-control

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

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

Is CVE-2017-20039 being exploited?

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

CVE-2017-20039 affects access control. Severity is critical (CVSS 9.8). A vulnerability was found in SICUNET Access Controller 0.32-05z. It has been classified as very critical. This affects an unknown part. The manipulation leads to weak authentication. It is possible to initiate the attack remotely.

How urgent is CVE-2017-20039?

Priority 57/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-39801 HIGH 7.5 DOWNGRADE SAP GRC Access control Emergency Access Management allows an authenticated attacker to access a Firefighter se
CVE-2021-44233 HIGH 8.8 DOWNGRADE SAP GRC Access Control - versions V1100_700, V1100_731, V1200_750, does not perform necessary authorization ch
CVE-2017-20040 MEDIUM 5.9 DOWNGRADE A vulnerability was found in SICUNET Access Controller 0.32-05z
CVE-2017-20038 MEDIUM 6.3 DOWNGRADE A vulnerability was found in SICUNET Access Controller 0.32-05z and classified as critical
CVE-2017-20037 MEDIUM 6.3 DOWNGRADE A vulnerability has been found in SICUNET Access Controller 0.32-05z and classified as critical

References

← Back to latest CVEs