KNX Association ETS5 up to 5.7.6 on Windows hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in KNX Association ETS5 up to 5.7.6 on Windows. It has been classified as problematic. This issue affects some unknown processing. This manipulation causes hard-coded credentials. This vulnerability is tracked as CVE-2021-36799. The attack is restricted to local execution. No exploit exists. Further encryption should be added.
Details
A vulnerability has been found in KNX Association ETS5 up to 5.7.6 on Windows and classified as problematic. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality.
The weakness was disclosed 07/19/2021 by Robert Gützkow. The advisory is shared at github.com. This vulnerability is known as CVE-2021-36799. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 23 days. During that time the estimated underground price was around $0-$5k.
It is possible to mitigate the problem by adding Project Store Directory as an encryption mechanism.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: EncryptionStatus: 🔍
0-Day Time: 🔍
Encryption: Project Store Directory
Timeline
06/26/2021 🔍07/19/2021 🔍
07/19/2021 🔍
07/19/2021 🔍
08/04/2024 🔍
Sources
Advisory: github.comResearcher: Robert Gützkow
Status: Not defined
CVE: CVE-2021-36799 (🔍)
GCVE (CVE): GCVE-0-2021-36799
GCVE (VulDB): GCVE-100-178897
Entry
Created: 07/19/2021 22:11Updated: 08/04/2024 03:35
Changes: 07/19/2021 22:11 (34), 07/22/2021 10:53 (2), 07/23/2021 18:35 (1), 07/23/2021 18:36 (8), 08/04/2024 03:35 (36)
Complete: 🔍
Committer: error-correction
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.