Use‑of‑Uninitialized Memory in libxls 1.6.3 During XLS Parsing
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Libxls | Libxls |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.242% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Libxls
Libxls libxls |
|
| Vendors & Products |
Libxls
Libxls libxls |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Use‑of‑Uninitialized Memory in libxls 1.6.3 During XLS Parsing |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Uninitialized Memory Use in libxls 1.6.3 Leads to Undefined Behavior and Possible Information Disclosure | |
| Weaknesses | CWE-758 |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Libxls Project
Libxls Project libxls |
|
| Weaknesses | CWE-908 | |
| CPEs | cpe:2.3:a:libxls_project:libxls:1.6.3:*:*:*:*:*:*:* | |
| Vendors & Products |
Libxls Project
Libxls Project libxls |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Uninitialized Memory Use in libxls 1.6.3 Leads to Undefined Behavior and Possible Information Disclosure | |
| Weaknesses | CWE-758 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A use-of-uninitialized memory vulnerability exists in libxls 1.6.3 when parsing malformed XLS files. The issue is reachable via xls_parseWorkBook() and is triggered by uninitialized heap memory originating from the OLE layer (ole2_read). The flaw is detectable with MemorySanitizer (MSAN) and can lead to undefined behavior, incorrect parsing logic, or potential information disclosure. | |
| References |
|