Asterisk 18.23.0/20.8.0/21.3.0 SIP Request incorrect implementation of authentication algorithm
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Asterisk 18.23.0/20.8.0/21.3.0. This affects an unknown function of the component SIP Request Handler. Executing a manipulation can lead to incorrect implementation of authentication algorithm. This vulnerability is tracked as CVE-2024-35190. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Asterisk 18.23.0/20.8.0/21.3.0. This vulnerability affects an unknown functionality of the component SIP Request Handler. The manipulation with an unknown input leads to a incorrect implementation of authentication algorithm vulnerability. The CWE definition for the vulnerability is CWE-303. The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect. As an impact it is known to affect confidentiality. CVE summarizes:
Asterisk is an open source private branch exchange and telephony toolkit. After upgrade to 18.23.0, ALL unauthorized SIP requests are identified as PJSIP Endpoint of local asterisk server. This vulnerability is fixed in 18.23.1, 20.8.1, and 21.3.1.
The advisory is available at github.com. This vulnerability was named CVE-2024-35190 since 05/10/2024. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 18.23.1, 20.8.1 or 21.3.1 eliminates this vulnerability. Applying the patch 85241bd22936cc15760fd1f65d16c98be7aeaf6d is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.8
CNA Vector (GitHub, Inc.): 🔍
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: Incorrect implementation of authentication algorithmCWE: CWE-303
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Asterisk 18.23.1/20.8.1/21.3.1
Patch: 85241bd22936cc15760fd1f65d16c98be7aeaf6d
Timeline
05/10/2024 🔍05/17/2024 🔍
05/17/2024 🔍
08/27/2025 🔍
Sources
Product: github.comAdvisory: GHSA-qqxj-v78h-hrf9
Status: Confirmed
CVE: CVE-2024-35190 (🔍)
GCVE (CVE): GCVE-0-2024-35190
GCVE (VulDB): GCVE-100-265042
Entry
Created: 05/17/2024 23:24Updated: 08/27/2025 00:42
Changes: 05/17/2024 23:24 (66), 08/27/2025 00:42 (11)
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.