# CVE-2017-20039: SICUNET Access Controller hard-coded password

> Remote attackers can exploit hard-coded credentials in SICUNET Access Controllers to bypass authentication and gain unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-mh4r-h7xh-h5pf

## What is CVE-2017-20039?

CVE-2017-20039 is a critical vulnerability in SICUNET Access Controller, published on 11 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2017-20039?

It affects 1 product.


Products: Sicunet Access Control.

## How do I fix CVE-2017-20039?

No fix has been published for CVE-2017-20039 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-20039 being exploited?

There is no known exploitation of CVE-2017-20039 in the wild and no public exploit code.

## Other vulnerabilities in SICUNET Access Controller

- [CVE-2017-20037](https://insights.sbomify.com/CVE-2017-20037/): SICUNET Access Controller privileges management (medium 6.3)
- [CVE-2017-20038](https://insights.sbomify.com/CVE-2017-20038/): SICUNET Access Controller card_scan_decoder.php privileges management (medium 6.3)
- [CVE-2017-20040](https://insights.sbomify.com/CVE-2017-20040/): SICUNET Access Controller Password Storage cleartext storage (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20039 and fix it if it is affected.

What it is: CVE-2017-20039 is a critical vulnerability in SICUNET Access Controller, published on 11 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-20039 in the wild and no public exploit code.

Affected product: SICUNET Access Controller. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-20039/ (Markdown: https://insights.sbomify.com/CVE-2017-20039/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-20039
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-20039
- OSV: https://osv.dev/vulnerability/CVE-2017-20039

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-20039/
Summaries are generated and may contain mistakes; the official description above is the record.