AudioCodes VoIP Desk Phone up to 3.4.4.1000 Backup libac_des3.so hard-coded key
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in AudioCodes VoIP Desk Phone up to 3.4.4.1000. It has been classified as problematic. Impacted is an unknown function in the library libac_des3.so of the component Backup Handler. The manipulation leads to hard-coded key. This vulnerability is documented as CVE-2023-22957. There is not any exploit available.
Details
A vulnerability was found in AudioCodes VoIP Desk Phone up to 3.4.4.1000 (IP Phone Software) and classified as problematic. This issue affects an unknown code block in the library libac_des3.so of the component Backup 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:
An issue was discovered in libac_des3.so on AudioCodes VoIP desk phones through 3.4.4.1000. Due to the use of hard-coded cryptographic key, an attacker with access to backup or configuration files is able to decrypt encrypted values and retrieve sensitive information, e.g., the device root password.
The weakness was released 08/12/2023 as SYSS-2022-052. It is possible to read the advisory at syss.de. The identification of this vulnerability is CVE-2023-22957 since 01/11/2023. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-27058). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.0VulDB Meta Temp Score: 2.0
VulDB Base Score: 2.0
VulDB Temp Score: 2.0
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: No
Local: No
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/11/2023 🔍08/12/2023 🔍
08/12/2023 🔍
10/05/2025 🔍
Sources
Advisory: SYSS-2022-052Status: Not defined
CVE: CVE-2023-22957 (🔍)
GCVE (CVE): GCVE-0-2023-22957
GCVE (VulDB): GCVE-100-237011
EUVD: 🔍
Entry
Created: 08/12/2023 10:03Updated: 10/05/2025 17:56
Changes: 08/12/2023 10:03 (41), 10/05/2025 17:56 (16)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.