CVE-2023-31475

An issue was discovered on GL.iNet devices before 3.216

Critical · published May 11, 2023

CVSS v3.1
9.0
EPSS
14%
Percentile
96.5
In the wild
Unconfirmed
What it is

🚨 A buffer overflow in GL.iNet devices could be your next 9-alarm fire! 🔥 Think of a crowded buffet where guests keep piling food onto a single plate without checking if it can hold it all — eventually, everything spills over. In the same way, this vulnerability allows unchecked data to overflow into memory, creating chaos. An attacker could exploit this vulnerability to execute arbitrary code, potentially gaining full control over the device. This could lead to unauthorized access, data breaches, or even turning the device into a malicious tool against its owner — absolutely devastating!

Put simply

Think of a crowded buffet where guests keep piling food onto a single plate without checking if it can hold it all — eventually, everything spills over. In the same way, this vulnerability allows unchecked data to overflow into memory, creating chaos. The buffer overflow occurs in the guci2_get() function of libglutil.so, where data from a UCI context is copied into a char pointer without proper size checks, leading to excessive memory usage and potential code execution.

What to do

An attacker could exploit this vulnerability to execute arbitrary code, potentially gaining full control over the device. This could lead to unauthorized access, data breaches, or even turning the device into a malicious tool against its owner — absolutely devastating! Update your GL.iNet devices to version 3.216 or later immediately. Ensure that all configurations are checked, and review your network security policies to mitigate potential risks. You've got this! Follow these steps, and you'll keep your devices safe and sound. 🛡️

The record
Technical detail
CVSS v3.1
9.0 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.13743 · 96.5th percentile
Published
2023-05-11T00:00Z
EPSS history
Timeline
  • 11 MAY 00:00Z
    An issue was discovered on GL.iNet devices before 3.216
    cvelistv5