9.8

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2022-48174

CVE-2022-48174: There is a stack overflow vulnerability in ash.c:6030 in busybox before 1.35. In the environment...

There is a stack overflow vulnerability in ash.c:6030 in busybox before 1.35. In the environment of Internet of Vehicles, this vulnerability can be executed from command to arbitrary code execution.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2022-48174

CVE-2022-48174:

9.8

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The analysis started by fetching content from the BusyBox bug tracker URL provided in the references. This revealed an ASAN stack trace and a patch for the vulnerability (CVE-2022-48174).

The ASAN trace clearly indicated a dynamic-stack-buffer-overflow in the evaluate_string function in shell/math.c. It also showed that evaluate_string was called by ash_arith in shell/ash.c at line 6030.
The CVE description explicitly states the vulnerability is in ash.c:6030.
The fetched patch content (attachment 9446 from the bug report, corresponding to an early fix attempt bf35d8bd) showed a modification to evaluate_string in shell/math.c. Specifically, it changed the alloca size for numstack. The line removed by this patch, var_or_num_t *const numstack = alloca((expr_len / 2) * sizeof(numstack[0]));, represents the vulnerable code that inadequately allocated space, leading to the overflow.
A later comment in the bug report mentioned a different commit (d417193cf) as the final fix, which further modified the allocation in evaluate_string to alloca(expr_len * sizeof(numstack[0])), confirming the allocation size was the core issue.

Based on this, evaluate_string is identified as the function containing the direct memory corruption vulnerability (insufficient alloca). ash_arith is identified as the function in ash.c that processes the potentially malicious input (the arithmetic expression from the shell) and calls evaluate_string, thereby triggering the vulnerability. Both functions would appear in a runtime profile during exploitation.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.