Wertheim SafeController Software for VAULT ROOMS 6.15.8328.28014 Configuration File SafeSystem.Infrastructure.Security.dll hard-coded key
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 6.30- |
Summary
A vulnerability, which was classified as problematic, has been found in Wertheim SafeController Software for VAULT ROOMS 6.15.8328.28014. This affects an unknown part in the library SafeSystem.Infrastructure.Security.dll of the component Configuration File Handler. The manipulation leads to hard-coded key. This vulnerability is traded as CVE-2026-34029. An attack has to be approached locally. There is no exploit available.
Details
A vulnerability was found in Wertheim SafeController Software for VAULT ROOMS 6.15.8328.28014. It has been rated as problematic. This issue affects an unknown functionality in the library SafeSystem.Infrastructure.Security.dll of the component Configuration File Handler. The manipulation with an unknown input leads to a hard-coded key vulnerability. Using CWE to declare the problem leads to CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. Impacted is confidentiality. The summary by CVE is:
The Wertheim SafeController Software, AssemblyVersion 6.15.8328.28014, contains a hard-coded cryptographic key in the SafeSystem.Infrastructure.Security.dll component. An attacker with access to the application files can reverse engineer the DLL and recover the hard-coded cryptographic key. This key can be used to decrypt the licence.whs file, which contains sensitive information about the licensing party and a second key that can be used to decrypt other configuration files.
The weakness was shared by Christian Hager. The advisory is shared at wertheim-safes.com. The identification of this vulnerability is CVE-2026-34029 since 03/25/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
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: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/25/2026 CVE reserved06/15/2026 Advisory disclosed
06/15/2026 VulDB entry created
06/15/2026 VulDB entry last update
Sources
Advisory: wertheim-safes.comResearcher: Christian Hager
Status: Not defined
CVE: CVE-2026-34029 (🔒)
GCVE (CVE): GCVE-0-2026-34029
GCVE (VulDB): GCVE-100-370889
Entry
Created: 06/15/2026 14:35Changes: 06/15/2026 14:35 (66)
Complete: 🔍
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.