# CVE-2022-3089: EnOcean SmartServer Hard-coded credentials

> Attackers can obtain cleartext credentials from a file to control the web interface and FTP server of the EnOcean SmartServer.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-r7ch-cwp4-rh7c

## What is CVE-2022-3089?

CVE-2022-3089 is a medium-severity vulnerability in EnOcean Smartserver, published on 13 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Echelon SmartServer 2.2 with i.LON Vision 2.2 stores cleartext credentials in a file, which could allow an attacker to obtain cleartext usernames and passwords of the SmartServer. If the attacker obtains the file, then the credentials could be used to control the web user interface and file transfer protocol (FTP) server.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-3089?

It affects 1 product.


Products: Echelon I.lon Vision.

## How do I fix CVE-2022-3089?

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

## Is CVE-2022-3089 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3089 and fix it if it is affected.

What it is: CVE-2022-3089 is a medium-severity vulnerability in EnOcean Smartserver, published on 13 Feb 2023. 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-2022-3089 in the wild and no public exploit code.

Affected product: EnOcean Smartserver. 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-2022-3089/ (Markdown: https://insights.sbomify.com/CVE-2022-3089/index.md)
```

## Sources

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

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