Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learningUpgrade exceljs-hardened to version 5.1.0 or higher.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via unbounded image anchor column parsing in Worksheet.getColumn, triggered when an application reads image positions from a workbook. An attacker can embed a drawing XML file (xl/drawings/drawing1.xml) containing an arbitrarily large anchor column index (e.g. 300000000), causing getImages() to walk the column list up to that index and allocate millions of Column objects until the process aborts with a fatal V8 heap out-of-memory error. Because the abort is a fatal V8 error, it cannot be caught with try/catch, making the denial of service unrecoverable.
In xl/drawings/drawing1.xml of a workbook containing an image:
<xdr:from><xdr:col>300000000</xdr:col> … </xdr:from>
const wb = new ExcelJS.Workbook(); await wb.xlsx.load(buffer); // 12 ms
wb.getWorksheet('S').getImages()[0].range.tl.col; // FATAL ERROR: ... JavaScript heap out of memory
With 3000000, the same read takes about 0.5 s and 640 MB of memory.