SpliceCom Maximiser Soft PBX up to 1.5 SSL Certificate channel accessible
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in SpliceCom Maximiser Soft PBX up to 1.5. Impacted is an unknown function of the component SSL Certificate. Such manipulation leads to channel accessible. This vulnerability is documented as CVE-2023-33760. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in SpliceCom Maximiser Soft PBX up to 1.5 (Communications System). It has been rated as problematic. Affected by this issue is an unknown code block of the component SSL Certificate. The manipulation with an unknown input leads to a channel accessible vulnerability. Using CWE to declare the problem leads to CWE-300. The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. Impacted is integrity. CVE summarizes:
SpliceCom Maximiser Soft PBX v1.5 and before was discovered to utilize a default SSL certificate. This issue can allow attackers to eavesdrop on communications via a man-in-the-middle attack.
The weakness was released 01/25/2024. The advisory is available at github.com. This vulnerability is handled as CVE-2023-33760 since 05/22/2023. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 06/18/2025). This vulnerability is assigned to T1557 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
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: Channel accessibleCWE: CWE-300
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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
05/22/2023 🔍01/25/2024 🔍
01/25/2024 🔍
06/18/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-33760 (🔍)
GCVE (CVE): GCVE-0-2023-33760
GCVE (VulDB): GCVE-100-252026
Entry
Created: 01/25/2024 09:18Updated: 06/18/2025 04:15
Changes: 01/25/2024 09:18 (38), 02/18/2024 13:00 (11), 06/18/2025 04:15 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.