yauzl 3.2.0 - Denial of Service via Off-by-One Error in NTFS Timestamp Parser
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| thejoshwolfe | yauzl | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Thejoshwolfe | Yauzl |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-gmq8-994r-jv83 | yauzl contains an off-by-one error |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.568% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Thejoshwolfe
Thejoshwolfe yauzl |
|
| Vendors & Products |
Thejoshwolfe
Thejoshwolfe yauzl |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | yauzl (aka Yet Another Unzip Library) version 3.2.0 for Node.js contains an off-by-one error in the NTFS extended timestamp extra field parser within the getLastModDate() function. The while loop condition checks cursor < data.length + 4 instead of cursor + 4 <= data.length, allowing readUInt16LE() to read past the buffer boundary. A remote attacker can cause a denial of service (process crash via ERR_OUT_OF_RANGE exception) by sending a crafted zip file with a malformed NTFS extra field. This affects any Node.js application that processes zip file uploads and calls entry.getLastModDate() on parsed entries. Fixed in version 3.2.1. | |
| Title | yauzl 3.2.0 - Denial of Service via Off-by-One Error in NTFS Timestamp Parser | |
| Weaknesses | CWE-193 | |
| References |
|
|
| Metrics |
cvssV3_1
|