voip_phones: Use of Hard-coded Credentials
CVE-2023-22956 is a high-severity use of hard-coded credentials vulnerability in voip_phones from AudioCodes, 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 voip_phones versions: 400HD. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.36% chance of exploitation within 30 days, higher than 72% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of voip_phones you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on syss.de for workarounds and exact fixed builds.
- 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 |
|---|---|---|---|
| Audiocodes Ltd | voip_phones | 400HD | Not stated |
| Audiocodes | C470hd Firmware | 3.4.4.1000 and earlier | Not stated |
| Audiocodes | C455hd Firmware | 3.4.4.1000 and earlier | Not stated |
| Audiocodes | C435hd Firmware | 3.4.4.1000 and earlier | Not stated |
| Audiocodes | 445hd Firmware | 3.4.4.1000 and earlier | Not stated |
| Audiocodes | 405hd Firmware | 3.4.4.1000 and earlier | Not stated |
| Audiocodes | C450hd Firmware | 3.4.4.1000 and earlier | 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
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
Official description
An issue was discovered on AudioCodes VoIP desk phones through 3.4.4.1000. Due to the use of a hard-coded cryptographic key, an attacker is able to decrypt encrypted configuration files and retrieve sensitive information.
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: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- seclists.org/fulldisclosure/2023/Aug/16Mailing List, Third Party Advisory
Technical write-ups (may include proof of concept)
- packetstormsecurity.com/files/174216/AudioCodes-VoIP-Phones-Hardcoded-Key.htmlExploit, Third Party Advisory, VDB Entry
Other references
- syss.deNot Applicable
Other vulnerabilities in voip_phones
- 7.5 High severity
- 7.8 High severity
Recent Use of Hard-coded Credentials vulnerabilities
- 7.2 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
Spotted an error? Tell us.