MB Connect Line mymbCONNECT24/mbCONNECT24 up to 2.6.1 com_mb24proxy cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in MB Connect Line mymbCONNECT24 and mbCONNECT24 up to 2.6.1. This affects an unknown part of the component com_mb24proxy. The manipulation results in cross-site request forgery. This vulnerability is known as CVE-2020-24570. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in MB Connect Line mymbCONNECT24 and mbCONNECT24 up to 2.6.1. Affected is an unknown function of the component com_mb24proxy. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:
An issue was discovered in MB CONNECT LINE mymbCONNECT24 and mbCONNECT24 through 2.6.1. There is a CSRF issue (with resultant SSRF) in the com_mb24proxy module, allowing attackers to steal session information from logged-in users with a crafted link.
The weakness was published 09/30/2020. This vulnerability is traded as CVE-2020-24570 since 08/21/2020. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.6.2 eliminates this vulnerability.
Similar entry is available at VDB-162119. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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: mymbCONNECT24/mbCONNECT24 2.6.2
Timeline
08/21/2020 🔍09/30/2020 🔍
10/01/2020 🔍
03/02/2021 🔍
Sources
Status: Not definedConfirmation: 🔍
CVE: CVE-2020-24570 (🔍)
GCVE (CVE): GCVE-0-2020-24570
GCVE (VulDB): GCVE-100-162120
See also: 🔍
Entry
Created: 10/01/2020 09:48Updated: 03/02/2021 08:13
Changes: 10/01/2020 09:48 (35), 10/01/2020 09:53 (3), 11/14/2020 09:33 (4), 11/15/2020 08:52 (1), 11/15/2020 08:54 (14), 03/02/2021 08:12 (1), 03/02/2021 08:13 (1)
Complete: 🔍
Committer: Anonymous User
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.