Teamcenter V12.4: Use of Hard-coded Credentials
CVE-2022-31619 is a high-severity use of hard-coded credentials vulnerability in Teamcenter V12.4 from Siemens, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Teamcenter V12.4 versions: All versions < V12.4.0.13. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.41% chance of exploitation within 30 days, higher than 73% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Teamcenter to 12.4.0.13 or 13.0.0.9 or 13.1.0.9 or 13.2.0.9, whichever matches your release line, or a later version.
- Read the advisory on cert-portal.siemens.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Siemens | Teamcenter V12.4 | All versions < V12.4.0.13 | Not stated |
| Siemens | Teamcenter V13.0 | All versions < V13.0.0.9 | Not stated |
| Siemens | Teamcenter V13.1 | All versions < V13.1.0.9 | Not stated |
| Siemens | Teamcenter V13.2 | All versions < V13.2.0.9 | Not stated |
| Siemens | Teamcenter V13.3 | All versions < V13.3.0.3 | Not stated |
| Siemens | Teamcenter V14.0 | All versions < V14.0.0.2 | Not stated |
| Siemens | Teamcenter | 12.4 up to, but not including, 12.4.0.13; 13.0 up to, but not including, 13.0.0.9; 13.1 up to, but not including, 13.1.0.9; 13.2 up to, but not including, 13.2.0.9; 13.3 up to, but not including, 13.3.0.3; 14.0 up to, but not including, 14.0.0.2 | 12.4.0.13, 13.0.0.9, 13.1.0.9, 13.2.0.9, 13.3.0.3, 14.0.0.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 2.0 | 6.5 | Medium | NVD |
Official description
A vulnerability has been identified in Teamcenter V12.4 (All versions < V12.4.0.13), Teamcenter V13.0 (All versions < V13.0.0.9), Teamcenter V13.1 (All versions < V13.1.0.9), Teamcenter V13.2 (All versions < V13.2.0.9), Teamcenter V13.3 (All versions < V13.3.0.3), Teamcenter V14.0 (All versions < V14.0.0.2). Java EE Server Manager HTML Adaptor in Teamcenter consists of default hardcoded credentials. Access to the application allows a user to perform a series of actions that could potentially lead to remote code execution with elevated permissions.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Hard-coded Credentials
The product contains hard-coded credentials, such as a password or cryptographic key.
How developers prevent this class of flaw
- For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible. In Windows environments, the Encrypted File System (EFS) may provide some protection.
- For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a first login mode that requires the user to enter a unique strong password or key.
- If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
More Use of Hard-coded Credentials vulnerabilities (CWE-798)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Teamcenter V12.4
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
Recent Use of Hard-coded Credentials vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.