Excelize: Unbounded row number in Rows.Columns makes GetRows and the Rows iterator loop for days
qax-os excelize
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/xuri/excelize/v2 Go |
|
|
| github.com/360EntSecGroup-Skylar/excelize/v2 Go |
| No fix yet |
qax-os excelize
| Product | Affected | Fixed in |
|---|---|---|
| github.com/xuri/excelize/v2 Go |
|
|
| github.com/360EntSecGroup-Skylar/excelize/v2 Go |
| No fix yet |
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.1.0 to 2.11.0, Rows.Columns accepts a look-ahead row number above TotalRows without applying the limit enforced by Rows.Next. File.GetRows relies on Rows.Next and Rows.Columns, but Rows.Columns consumes the row r attribute without the limit check in Rows.Next. When a crafted worksheet places an oversized row number after an ordinary valid row and the application calls GetRows or iterates Rows, the iterator advances through every missing row number instead of rejecting the workbook, allowing an attacker to consume a CPU core for an attacker-controlled duration. No fixed version is available as of this review.
From the CVE record · GitHub_M
Excelize can spend an attacker-controlled amount of time advancing through missing rows when an application processes a crafted worksheet with GetRows or iterates Rows. The worksheet must place an oversized row number after a valid row; processing it can consume a CPU core.
Check applications using Go github.com/xuri/excelize/v2 from 2.1.0 before 2.11.1-0.20260930021559-01a9ff32fb3c, or github.com/360EntSecGroup-Skylar/excelize/v2 from 2.1.0 onward.