VYPR
Vendor

Libxls

Products
1
CVEs
20
Across products
20
Status
Private

Products

1

Recent CVEs

20
  • CVE-2017-12109HigApr 24, 2018
    risk 0.57cvss 8.8epss 0.03

    An exploitable integer overflow vulnerability exists in the xls_preparseWorkSheet function of libxls 1.4 when handling a MULRK record. A specially crafted XLS file can cause a memory corruption resulting in remote code execution. An attacker can send malicious XLS file to…

  • CVE-2017-12108HigApr 24, 2018
    risk 0.57cvss 8.8epss 0.03

    An exploitable integer overflow vulnerability exists in the xls_preparseWorkSheet function of libxls 1.4 when handling a MULBLANK record. A specially crafted XLS file can cause a memory corruption resulting in remote code execution. An attacker can send malicious XLS file to…

  • CVE-2017-12111HigNov 20, 2017
    risk 0.57cvss 8.8epss 0.02

    An exploitable out-of-bounds vulnerability exists in the xls_addCell function of libxls 1.4. A specially crafted XLS file with a formula record can cause memory corruption resulting in remote code execution. An attacker can send a malicious XLS file to trigger this vulnerability.

  • CVE-2017-12110HigNov 20, 2017
    risk 0.57cvss 8.8epss 0.02

    An exploitable integer overflow vulnerability exists in the xls_appendSST function of libxls 1.4.A specially crafted XLS file can cause memory corruption resulting in remote code execution.

  • CVE-2017-2919HigNov 20, 2017
    risk 0.51cvss 7.8epss 0.02

    An exploitable stack based buffer overflow vulnerability exists in the xls_getfcell function of libxls 1.3.4. A specially crafted XLS file can cause a memory corruption resulting in remote code execution. An attacker can send malicious XLS file to trigger this vulnerability

  • CVE-2017-2897HigNov 20, 2017
    risk 0.51cvss 7.8epss 0.02

    An exploitable out-of-bounds write vulnerability exists in the read_MSAT function of libxls 1.4. A specially crafted XLS file can cause a memory corruption resulting in remote code execution. An attacker can send malicious XLS file to trigger this vulnerability.

  • CVE-2017-2896HigNov 20, 2017
    risk 0.51cvss 7.8epss 0.02

    An exploitable out-of-bounds write vulnerability exists in the xls_mergedCells function of libxls 1.4. . A specially crafted XLS file can cause a memory corruption resulting in remote code execution. An attacker can send malicious XLS file to trigger this vulnerability.

  • CVE-2026-26824MedJun 3, 2026
    risk 0.42cvss 6.5epss 0.00

    libxls through version 1.6.3 contains a use of uninitialized memory vulnerability in the OLE container parser. Memory allocated for the Master Sector Allocation Table (MSAT) in read_MSAT() is not fully initialized before being consumed by ole2_validate_sector_chain(), which may…

  • CVE-2026-26825MedJun 3, 2026
    risk 0.34cvss 5.3epss 0.00

    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…

  • CVE-2023-38851Aug 15, 2023
    risk 0.00cvss epss 0.01

    Buffer Overflow vulnerability in libxlsv.1.6.2 allows a remote attacker to execute arbitrary code and cause a denial of service via a crafted XLS file to the xls_parseWorkBook function in xls.c:1018.

  • CVE-2023-38853Aug 15, 2023
    risk 0.00cvss epss 0.01

    Buffer Overflow vulnerability in libxlsv.1.6.2 allows a remote attacker to execute arbitrary code and cause a denial of service via a crafted XLS file to the xls_parseWorkBook function in xls.c:1015.

  • CVE-2023-38855Aug 15, 2023
    risk 0.00cvss epss 0.01

    Buffer Overflow vulnerability in libxlsv.1.6.2 allows a remote attacker to execute arbitrary code and cause a denial of service via a crafted XLS file to the get_string function in xlstool.c:395.

  • CVE-2023-38856Aug 15, 2023
    risk 0.00cvss epss 0.01

    Buffer Overflow vulnerability in libxlsv.1.6.2 allows a remote attacker to execute arbitrary code and cause a denial of service via a crafted XLS file to the get_string function in xlstool.c:411.

  • CVE-2023-38852Aug 15, 2023
    risk 0.00cvss epss 0.01

    Buffer Overflow vulnerability in libxlsv.1.6.2 allows a remote attacker to execute arbitrary code and cause a denial of service via a crafted XLS file to the unicode_decode_wcstombs function in xlstool.c:266.

  • CVE-2023-38854Aug 15, 2023
    risk 0.00cvss epss 0.01

    Buffer Overflow vulnerability in libxlsv.1.6.2 allows a remote attacker to execute arbitrary code and cause a denial of service via a crafted XLS file to the transcode_latin1_to_utf8 function in xlstool.c:296.

  • CVE-2021-27836Nov 3, 2021
    risk 0.00cvss epss 0.01

    An issue was discoverered in in function xls_getWorkSheet in xls.c in libxls 1.6.2, allows attackers to cause a denial of service, via a crafted XLS file.

  • CVE-2020-27819Feb 23, 2021
    risk 0.00cvss epss 0.01

    An issue was discovered in libxls before and including 1.6.1 when reading Microsoft Excel files. A NULL pointer dereference vulnerability exists when parsing XLS cells in libxls/xls2csv.c:199. It could allow a remote attacker to cause a denial of service via crafted XLS file.

  • CVE-2017-2910Dec 2, 2020
    risk 0.00cvss epss 0.02

    An exploitable Out-of-bounds Write vulnerability exists in the xls_addCell function of libxls 2.0. A specially crafted xls file can cause a memory corruption resulting in remote code execution. An attacker can send malicious xls file to trigger this vulnerability.

  • CVE-2018-20450Dec 25, 2018
    risk 0.00cvss epss 0.01

    The read_MSAT function in ole.c in libxls 1.4.0 has a double free that allows attackers to cause a denial of service (application crash) via a crafted file, a different vulnerability than CVE-2017-2897.

  • CVE-2018-20452Dec 25, 2018
    risk 0.00cvss epss 0.02

    The read_MSAT_body function in ole.c in libxls 1.4.0 has an invalid free that allows attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted file, because of inconsistent memory management (new versus free) in…