moby up to 26.0.2 image_history.go null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in moby up to 26.0.2. It has been classified as problematic. This affects an unknown function of the file daemon/images/image_history.go. This manipulation causes null pointer dereference. The identification of this vulnerability is CVE-2024-36620. There is no exploit available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in moby up to 26.0.2. It has been declared as problematic. Affected by this vulnerability is an unknown code block of the file daemon/images/image_history.go. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:
moby v25.0.0 - v26.0.2 is vulnerable to NULL Pointer Dereference via daemon/images/image_history.go.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2024-36620 since 05/30/2024. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 276314 (TencentOS Server 4: moby (TSSA-2024:1079)), which helps to determine the existence of the flaw in a target environment.
Applying the patch ab570ab3d62038b3d26f96a9bb585d0b6095b9b4 is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at Tenable (276314). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/moby/moby/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (MITRE): 🔍
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: Null pointer dereferenceCWE: CWE-476 / CWE-404
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 |
Nessus ID: 276314
Nessus Name: TencentOS Server 4: moby (TSSA-2024:1079)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: ab570ab3d62038b3d26f96a9bb585d0b6095b9b4
Timeline
05/30/2024 🔍11/29/2024 🔍
11/29/2024 🔍
11/24/2025 🔍
Sources
Product: github.comAdvisory: ab570ab3d62038b3d26f96a9bb585d0b6095b9b4
Status: Confirmed
CVE: CVE-2024-36620 (🔍)
GCVE (CVE): GCVE-0-2024-36620
GCVE (VulDB): GCVE-100-286459
Entry
Created: 11/29/2024 22:58Updated: 11/24/2025 00:25
Changes: 11/29/2024 22:58 (56), 12/05/2024 02:04 (12), 11/24/2025 00:25 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.