| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in mooSocial 3.1.8. The affected element is an unknown function of the component DNS Request Handler. This manipulation of the argument messageText/data[wall_photo]/data[userShareVideo]/data[userShareLink] causes an unknown weakness. The identification of this vulnerability is CVE-2023-43323. There is no exploit available.
Details
A vulnerability was found in mooSocial 3.1.8. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the component DNS Request Handler. The manipulation of the argument messageText/data[wall_photo]/data[userShareVideo]/data[userShareLink] with an unknown input leads to a unknown weakness. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
mooSocial 3.1.8 is vulnerable to external service interaction on post function. When executed, the server sends a HTTP and DNS request to external server. The Parameters effected are multiple - messageText, data[wall_photo], data[userShareVideo] and data[userShareLink].
The weakness was shared 09/28/2023. The advisory is shared at github.com. This vulnerability is known as CVE-2023-43323 since 09/18/2023. Technical details are known, but no exploit is available.
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 the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: Privilege escalationCWE: Unknown
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
09/18/2023 🔍09/28/2023 🔍
09/28/2023 🔍
09/25/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-43323 (🔍)
GCVE (CVE): GCVE-0-2023-43323
GCVE (VulDB): GCVE-100-240829
Entry
Created: 09/28/2023 23:28Updated: 09/25/2024 13:07
Changes: 09/28/2023 23:28 (36), 10/21/2023 17:10 (11), 09/25/2024 13:07 (15)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.