Excelize: Unbounded spinCount in agile decryption burns CPU during OpenFile
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.3.1 to 2.11.0, agile decryption accepts an attacker-controlled spinCount and performs that many password-key derivation iterations before verifier validation. OpenFile reaches agileDecrypt, which passes the unbounded spinCount to convertPasswdToKey before password verification. When a crafted OLE encrypted-workbook header supplies an excessive spinCount and the file is opened, the key-derivation loop performs unbounded attacker-selected work and cannot be cancelled, 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 accepts an unbounded spinCount from an encrypted-workbook header before verifying the password. If a crafted workbook is opened, an attacker can make key derivation consume a CPU core for an attacker-controlled duration; the work cannot be cancelled.
Teams using Go package github.com/xuri/excelize/v2 or github.com/360EntSecGroup-Skylar/excelize/v2 from version 2.3.1 onward should check their dependencies.