Excelize Decrypt: unrecoverable panics on malformed OLE/CFB encrypted workbooks
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, the decryption dispatch performs insufficient structural and parameter validation before standard and agile decryptors slice, index, allocate, and divide using attacker-controlled values. Decrypt passes attacker-controlled EncryptionInfo and EncryptedPackage data into standardDecrypt or agileDecrypt before validating the structures used by those routines. When a malformed OLE compound file with a version-valid EncryptionInfo stream is opened or passed to Decrypt, nine malformed-input classes reach unrecovered Go runtime panics instead of the documented error path, allowing an attacker to terminate the calling process. No fixed version is available as of this review.
From the CVE record · GitHub_M
Excelize insufficiently validates attacker-controlled encryption data before passing it to its decryptors. If an application opens or decrypts a malformed OLE compound file with a version-valid EncryptionInfo stream, the input can trigger an unrecovered Go panic and terminate the process.
Check applications using Go github.com/xuri/excelize/v2 from 2.3.1 before 2.11.1-0.20260915055537-22f76f9acb94, or github.com/360EntSecGroup-Skylar/excelize/v2 from 2.3.1 onward.