mipjz 5.0.5 ApiAdminTool.php mipPost postAddress server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in mipjz 5.0.5. It has been rated as critical. Affected by this issue is the function mipPost of the file \app\setting\controller\ApiAdminTool.php. The manipulation of the argument postAddress leads to server-side request forgery.
This vulnerability is handled as CVE-2024-48232. There is no exploit available.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability was found in mipjz 5.0.5. It has been declared as problematic. Affected by this vulnerability is the function mipPost of the file \app\setting\controller\ApiAdminTool.php. The manipulation of the argument postAddress with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality. The summary by CVE is:
An issue was found in mipjz 5.0.5. In the mipPost method of \app\setting\controller\ApiAdminTool.php, the value of the postAddress parameter is not processed and is directly passed into curl_exec execution and output, resulting in a Server-side request forgery (SSRF) vulnerability that can read server files.
The advisory is shared at github.com. This vulnerability is known as CVE-2024-48232 since 10/08/2024. The exploitation appears to be easy. Technical details are known, but no exploit is available.
By approaching the search of inurl:\app\setting\controller\ApiAdminTool.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
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: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Local: No
Remote: Partially
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/08/2024 CVE reserved10/25/2024 Advisory disclosed
10/25/2024 VulDB entry created
10/25/2024 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2024-48232 (🔒)
GCVE (CVE): GCVE-0-2024-48232
GCVE (VulDB): GCVE-100-281905
Entry
Created: 10/25/2024 11:16 PMChanges: 10/25/2024 11:16 PM (54)
Complete: 🔍
Cache ID: 18:61D:40
No comments yet. Languages: en.
Please log in to comment.