CVE-2025-13120
BaseFortify
Publication date: 2025-11-13
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mruby | mruby | to 3.4.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the mruby software up to version 3.4.0, specifically in the function sort_cmp within the src/array.c file. It causes a use after free condition, which means the program may attempt to use memory after it has been freed, potentially leading to unexpected behavior or crashes. Exploitation requires local access to the system.
How can this vulnerability impact me? :
The vulnerability can lead to partial compromise of confidentiality, integrity, and availability of the affected system, as indicated by the CVSS scores. Since it is a use after free issue exploitable locally, an attacker with local access could potentially cause the program to behave unpredictably, possibly leading to data corruption, crashes, or other security impacts.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to implement the patch named eb398971bfb43c38db3e04528b68ac9a7ce509bc that corrects the issue in mruby up to version 3.4.0.