# CVE-2017-13740: Memory corruption in n/a

> A stack-based buffer overflow in Liblouis allows attackers to cause denial of service or potentially execute arbitrary code.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-13740, GHSA-72qw-xhg7-3mhv, UBUNTU-CVE-2017-13740

## What is CVE-2017-13740?

CVE-2017-13740 is a high-severity memory corruption vulnerability in n/a, published on 29 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

There is a stack-based buffer overflow in Liblouis 3.2.0, triggered in the function parseChars() in compileTranslationTable.c, that will lead to denial of service or possibly unspecified other impact.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-13740?

It affects 1 product.


Products: Liblouis Liblouis.

## How do I fix CVE-2017-13740?

Upgrade to a fixed version.

## Is CVE-2017-13740 being exploited?

There is no known exploitation of CVE-2017-13740 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-13738](https://insights.sbomify.com/CVE-2017-13738/): Memory corruption in n/a (high 8.8)
- [CVE-2017-13739](https://insights.sbomify.com/CVE-2017-13739/): Memory corruption in n/a (high 8.8)
- [CVE-2014-8184](https://insights.sbomify.com/CVE-2014-8184/): Memory corruption in liblouis (high 7.8)
- [CVE-2017-15101](https://insights.sbomify.com/CVE-2017-15101/): Memory corruption in liblouis (high 7.8)
- [CVE-2023-26767](https://insights.sbomify.com/CVE-2023-26767/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13740 and fix it if it is affected.

What it is: CVE-2017-13740 is a high-severity memory corruption vulnerability in n/a, published on 29 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-13740 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-13740/ (Markdown: https://insights.sbomify.com/CVE-2017-13740/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-13740
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-13740
- OSV: https://osv.dev/vulnerability/CVE-2017-13740

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-13740/
Summaries are generated and may contain mistakes; the official description above is the record.