EnOcean SmartServer Hard-coded credentials

published 2023-02-13 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-42518

cvss: 6.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits: 0; none known

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-23-037-01 updated 2023-02-07 cvss 6.3

EnOcean SmartServer

EnOcean Edge Inc, a subsidiary of EnOcean GmbH- EnOcean SmartServer v2.2 SR8/SP8 (4.12.006) with i.LON Vision v2.2 SR8/SP8 (4.12.006)
affected: mitigation “EnOcean Edge released SmartServer 3.5 Update 2 (v3.52.003).” enoceanwiki.atlassian.net

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 21 mo ago (2025-01-16)

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.3	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:H
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

EnOcean Smartserver

Classification

Weakness

CWE-798 Use of Hard-coded Credentials
CWE-312 Cleartext Storage of Sensitive Information

References

cisa.gov /uscert/ics/advisories/icsa-23-037-01
broken-link

Sources

CVE List CVE-2022-3089
NVD CVE-2022-3089

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary