IP-HE950E: Use of Hard-coded Credentials
CVE-2023-38433 is a high-severity use of hard-coded credentials vulnerability in IP-HE950E from Fujitsu, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected IP-HE950E versions: firmware versions V01L001 to V01L053; V01L001 through V01L053. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 3.72% chance of exploitation within 30 days, higher than 90% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of IP-HE950E you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Fujitsu | IP-HE950E | firmware versions V01L001 to V01L053; V01L001 through V01L053 | Not stated |
| Fujitsu | IP-HE950D | firmware versions V01L001 to V01L053 | Not stated |
| Fujitsu | IP-HE900E | firmware versions V01L001 to V01L010 | Not stated |
| Fujitsu | IP-HE900D | firmware versions V01L001 to V01L004 | Not stated |
| Fujitsu | IP-900E / IP-920E | firmware versions V01L001 to V02L061 | Not stated |
| Fujitsu | IP-900D / IP-900ⅡD / IP-920D | firmware versions V01L001 to V02L061 | Not stated |
| Fujitsu | IP-90 | firmware versions V01L001 to V01L013; V01L001 through V01L013 | Not stated |
| Fujitsu | IP-9610 | firmware versions V01L001 to V02L007 | Not stated |
| Fujitsu | ip-he950d_firmware | v01l001 through V01L053 | Not stated |
| Fujitsu | ip-he900e_firmware | v01l001 through V01L010 | Not stated |
| Fujitsu | ip-he900d_firmware | v01l001 through V01L004 | Not stated |
| Fujitsu | ip-900e_firmware | v01l001 through V02L061 | Not stated |
| Fujitsu | ip-920e_firmware | v01l001 through V02L061 | Not stated |
| Fujitsu | ip-900d_firmware | v01l001 through V02L061 | Not stated |
| Fujitsu | ip-900iid_firmware | v01l001 through V02L061 | Not stated |
| Fujitsu | ip-920d_firmware | v01l001 through V02L061 | Not stated |
| Fujitsu | ip-9610_firmware | v01l001 through V02L007 | Not stated |
| Fujitsu | Ip-he950e Firmware | v01l001 through v01l053 | Not stated |
| Fujitsu | Ip-90 Firmware | v01l001 through v01l013 | Not stated |
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
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
Official description
Fujitsu Real-time Video Transmission Gear "IP series" use hard-coded credentials, which may allow a remote unauthenticated attacker to initialize or reboot the products, and as a result, terminate the video transmission. Affected products and versions are as follows: IP-HE950E firmware versions V01L001 to V01L053, IP-HE950D firmware versions V01L001 to V01L053, IP-HE900E firmware versions V01L001 to V01L010, IP-HE900D firmware versions V01L001 to V01L004, IP-900E / IP-920E firmware versions V01L001 to V02L061, IP-900D / IP-900ⅡD / IP-920D firmware versions V01L001 to V02L061, IP-90 firmware versions V01L001 to V01L013, and IP-9610 firmware versions V01L001 to V02L007.
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.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- jvn.jp/en/jp/JVN95727578/Third Party Advisory
Other references
Recent Use of Hard-coded Credentials vulnerabilities
- 7.5 High severity
- 9.1 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.