Minio S3 Server allocation of file descriptors or handles without limits or throttling
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Minio S3 Server. This impacts an unknown function. This manipulation causes allocation of file descriptors or handles without limits or throttling. This vulnerability appears as CVE-2018-1000538. The attack may be initiated remotely. There is no available exploit. It is suggested to install a patch to address this issue.
Details
A vulnerability classified as problematic was found in Minio S3 Server (affected version unknown). Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a allocation of file descriptors or handles without limits or throttling vulnerability. The CWE definition for the vulnerability is CWE-774. The product allocates file descriptors or handles on behalf of an actor without imposing any restrictions on how many descriptors can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability. The summary by CVE is:
Minio Inc. Minio S3 server version prior to RELEASE.2018-05-16T23-35-33Z contains a Allocation of Memory Without Limits or Throttling (similar to CWE-774) vulnerability in write-to-RAM that can result in Denial of Service. This attack appear to be exploitable via Sending V4-(pre)signed requests with large bodies . This vulnerability appears to have been fixed in after commit 9c8b7306f55f2c8c0a5c7cea9a8db9d34be8faa7.
The bug was discovered 05/18/2018. The weakness was presented 06/26/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-1000538 since 06/22/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 39 days. During that time the estimated underground price was around $0-$5k.
Applying the patch 9c8b7306f55f2c8c0a5c7cea9a8db9d34be8faa7 is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Allocation of file descriptors or handles without limits or throttlingCWE: CWE-774
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 9c8b7306f55f2c8c0a5c7cea9a8db9d34be8faa7
Timeline
05/18/2018 🔍06/22/2018 🔍
06/26/2018 🔍
06/26/2018 🔍
06/27/2018 🔍
03/29/2023 🔍
Sources
Advisory: 9c8b7306f55f2c8c0a5c7cea9a8db9d34be8faa7Status: Not defined
CVE: CVE-2018-1000538 (🔍)
GCVE (CVE): GCVE-0-2018-1000538
GCVE (VulDB): GCVE-100-119953
Entry
Created: 06/27/2018 10:05Updated: 03/29/2023 08:00
Changes: 06/27/2018 10:05 (56), 02/22/2020 13:47 (1), 03/29/2023 08:00 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.