Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1632834 - (CVE-2018-17294) CVE-2018-17294 liblouis: Stack-based buffer over-read in matchCurrentInput function lou_translateString.c
CVE-2018-17294 liblouis: Stack-based buffer over-read in matchCurrentInput fu...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20180924,reported=2...
: Security
Depends On: 1632837 1632836
Blocks: 1632835
  Show dependency tree / graph
 
Reported: 2018-09-25 11:58 EDT by Pedro Sampaio
Modified: 2018-10-30 17:26 EDT (History)
2 users (show)

See Also:
Fixed In Version: liblouis 3.7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Pedro Sampaio 2018-09-25 11:58:51 EDT 
The matchCurrentInput function inside lou_translateString.c of Liblouis prior to 3.7 does not check the input string's length, allowing attackers to cause a denial of service (application crash via out-of-bounds read) by crafting an input file with certain translation dictionaries.

Upstream patch:

https://github.com/liblouis/liblouis/commit/5e4089659bb49b3095fa541fa6387b4c40d7396e

Upstream issue:

https://github.com/liblouis/liblouis/issues/635
Comment 1 Pedro Sampaio 2018-09-25 11:59:50 EDT 
Created liblouis tracking bugs for this issue:

Affects: fedora-all [bug 1632836]
Comment 3 Scott Gayou 2018-10-30 17:26:20 EDT 
Rebuilt with ASAN. No crashes, no errors. Same with Valgrind. Source has similar potentially vulnerable code, i.e. matchcurrentInput, but since this didn't trigger and is low, closing as NOTAFFECTED instead of going deeper into this.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.