PlaySMS up to 1.4.5 /auth/fn.php improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in PlaySMS up to 1.4.5. This issue affects some unknown processing of the file /auth/fn.php. Performing a manipulation results in improper authentication. This vulnerability is identified as CVE-2022-47034. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as critical has been found in PlaySMS up to 1.4.5. This affects an unknown functionality of the file /auth/fn.php. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A type juggling vulnerability in the component /auth/fn.php of PlaySMS v1.4.5 and earlier allows attackers to bypass authentication.
The weakness was released 02/14/2023 as dd23673a00c052e113c6d44eb629dc355d3c0605. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-47034 since 12/12/2022. Technical details of the vulnerability are known, but there is no available exploit.
By approaching the search of inurl:auth/fn.php it is possible to find vulnerable targets with Google Hacking.
Applying the patch dd23673a00c052e113c6d44eb629dc355d3c0605 is able to eliminate this problem. The bugfix is ready for download at github.com.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/playsms/playsms/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: dd23673a00c052e113c6d44eb629dc355d3c0605
Timeline
12/12/2022 🔍02/14/2023 🔍
02/14/2023 🔍
03/12/2023 🔍
Sources
Product: github.comAdvisory: dd23673a00c052e113c6d44eb629dc355d3c0605
Status: Confirmed
CVE: CVE-2022-47034 (🔍)
GCVE (CVE): GCVE-0-2022-47034
GCVE (VulDB): GCVE-100-220851
Entry
Created: 02/14/2023 11:27Updated: 03/12/2023 12:22
Changes: 02/14/2023 11:27 (41), 03/12/2023 12:22 (11)
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.