# CVE-2021-36799: Hardcoded credentials in n/a

> Local attackers can read project information using hard-coded credentials in the unsupported KNX ETS5 desktop application.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jj35-9m2c-j64q

## What is CVE-2021-36799?

CVE-2021-36799 is a high-severity vulnerability in n/a, published on 19 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

KNX ETS5 through 5.7.6 uses the hard-coded password ETS5Password, with a salt value of Ivan Medvedev, allowing local users to read project information. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

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

## Which versions are affected by CVE-2021-36799?

It affects 1 product.


Products: Knx Engineering Tool Software 5.

## How do I fix CVE-2021-36799?

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

## Is CVE-2021-36799 being exploited?

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

Public exploit code:

- ETS5 Password Recovery Tool is a PoC for CVE-2021-36799 (github_poc): https://github.com/robertguetzkow/ets5-password-recovery

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-36799 and fix it if it is affected.

What it is: CVE-2021-36799 is a high-severity vulnerability in n/a, published on 19 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-36799 in the wild and no public exploit code.

Affected product: n/a. 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-2021-36799/ (Markdown: https://insights.sbomify.com/CVE-2021-36799/index.md)
```

## Sources

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

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