Heap Overflow in Excelize via Missing Drawing Element Check

Executive Summary

This is a nil pointer dereference vulnerability in the Excelize Go library. It occurs when GetSlicers checks for ExtLst but fails to verify if the optional drawing element exists. If a crafted worksheet contains an extLst without a drawing element, the code attempts to access ws.Drawing.RID, causing a panic and process termination.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by checking if your system uses Excelize library versions 2.9.0 to 2.11.0. Inspect Go module files or dependencies for the Excelize package version. No specific commands are provided in the context to exploit or detect this issue actively.

Useful 0 Not Useful 0

Impact Analysis

An attacker could exploit this to crash applications using vulnerable versions of Excelize (2.9.0 to 2.11.0). This could lead to denial of service, data loss, or unexpected application behavior if not handled properly.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability does not directly affect compliance with GDPR or HIPAA. It is a nil-pointer dereference issue causing a denial-of-service (DoS) condition in the Excelize library. Compliance impacts would only occur if the DoS disrupts systems processing personal or health data, but the CVE itself does not address data handling or regulatory requirements.

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include upgrading to a version of Excelize outside the vulnerable range (2.9.0 to 2.11.0) if available. Since no fixed version is available as of the review, consider temporarily disabling the GetSlicers functionality or applying input validation for crafted worksheets. Monitor for updates from the library maintainers.

Useful 0 Not Useful 0