Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-13743

liblouis: Buffer overflow in the function _lou_showString()

Overview

Published
29 Aug 2017
Modified
17 Jun 2026
Medium CVE
0 Registry packages
9 OS packages
5 Linux distributions
Yes Fix available

Description

There is a buffer overflow in Liblouis 3.2.0, triggered in the function _lou_showString() in utils.c, that will lead to a remote denial of service attack.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Weakness: CWE-119

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

Oracle Linux 1 release · 1 package

fixed 1
liblouis
Oracle Linux fixes for CVE-2017-13743
ReleasePackageFixed in
7 liblouis +4 2.5.2-11.el7_4

Red Hat 1 release · 1 package

fixed 1
liblouis
Red Hat fixes for CVE-2017-13743
ReleasePackageFixed inAdvisory
7 liblouis +4 0:2.5.2-11.el7_4 RHSA-2017:3111

debian 5 releases · 1 package

fixed 5
liblouis
debian fixes for CVE-2017-13743
ReleasePackageFixed in
11 liblouis 3.3.0-1
12 liblouis 3.3.0-1
13 liblouis 3.3.0-1
14 liblouis 3.3.0-1
9 liblouis 3.0.0-3+deb9u1

echo 1 release · 1 package

fixed 1
liblouis
echo fixes for CVE-2017-13743
ReleasePackageFixed in
liblouis 3.3.0-1

openSUSE 1 release · 1 package

fixed 1
liblouis-data
openSUSE fixes for CVE-2017-13743
ReleasePackageFixed inAdvisory
Tumbleweed liblouis-data +5 3.16.1-1.5 openSUSE-SU-2024:10953-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.