miniSphere up to 5.0.2/5.1.4/5.2.9 map_engine.c layer_resize integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in miniSphere up to 5.0.2/5.1.4/5.2.9. The impacted element is the function layer_resize of the file map_engine.c. The manipulation results in integer overflow.
This vulnerability is known as CVE-2018-1000524. Attacking locally is a requirement. No exploit is available.
You should upgrade the affected component.
Details
A vulnerability was found in miniSphere up to 5.0.2/5.1.4/5.2.9. It has been classified as critical. Affected is the function layer_resize of the file map_engine.c. The manipulation with an unknown input leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
miniSphere version 5.2.9 and earlier contains a Integer Overflow vulnerability in layer_resize() function in map_engine.c that can result in remote denial of service. This attack appear to be exploitable via the victim must load a specially-crafted map which calls SetLayerSize in its entry script. This vulnerability appears to have been fixed in 5.0.3, 5.1.5, 5.2.10 and later.
The bug was discovered 06/13/2018. The weakness was published 06/26/2018 (Website). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2018-1000524 since 06/22/2018. 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 known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 13 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 5.0.3, 5.1.5 or 5.2.10 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
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.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.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: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: miniSphere 5.0.3/5.1.5/5.2.10
Patch: github.com
Timeline
06/13/2018 🔍06/22/2018 🔍
06/26/2018 🔍
06/26/2018 🔍
06/27/2018 🔍
03/28/2023 🔍
Sources
Advisory: 252c1ca184cb38e1acb917aa0e451c5f08519996Status: Not defined
CVE: CVE-2018-1000524 (🔍)
GCVE (CVE): GCVE-0-2018-1000524
GCVE (VulDB): GCVE-100-119940
Entry
Created: 06/27/2018 08:47Updated: 03/28/2023 21:22
Changes: 06/27/2018 08:47 (58), 02/22/2020 11:24 (1), 03/28/2023 21:07 (5), 03/28/2023 21:22 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.