CVE-2025-7207
BaseFortify
Publication date: 2025-07-09
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 (exc) |
| mruby | mruby | 3.4.0 |
| mruby | mruby | 3.4.0 |
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-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a heap-based buffer overflow found in the mruby project up to version 3.4.0-rc2, specifically in the function scope_new within the file mrbgems/mruby-compiler/core/codegen.c. It occurs due to improper manipulation in the nregs Handler component. Exploiting this vulnerability requires local access to the system. The issue has been publicly disclosed and a patch is available to fix it.
How can this vulnerability impact me? :
The vulnerability can lead to a heap-based buffer overflow, which may cause unexpected behavior such as crashes or potentially allow an attacker with local access to execute arbitrary code or disrupt the normal operation of the affected software. Since the attack requires local access, remote exploitation is not possible.
What immediate steps should I take to mitigate this vulnerability?
It is recommended to apply the patch named 1fdd96104180cc0fb5d3cb086b05ab6458911bb9 to fix this issue.