Bug 1860324 (CVE-2020-15890) - CVE-2020-15890 luajit: out-of-bounds read because __gc handler frame traversal is mishandled
Summary: CVE-2020-15890 luajit: out-of-bounds read because __gc handler frame traversa...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2020-15890
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1860330 1860331 1861551
Blocks: 1860329
TreeView+ depends on / blocked
 
Reported: 2020-07-24 10:17 UTC by Dhananjay Arunesh
Modified: 2021-06-07 15:09 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in luajit. An out-of-bounds read can occur due to a frame traversal being mishandled.
Clone Of:
Environment:
Last Closed: 2020-07-31 07:27:41 UTC
Embargoed:


Attachments (Terms of Use)

Description Dhananjay Arunesh 2020-07-24 10:17:55 UTC
LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled.

References
https://github.com/LuaJIT/LuaJIT/issues/601

Comment 1 Dhananjay Arunesh 2020-07-24 10:20:44 UTC
Created luajit tracking bugs for this issue:

Affects: epel-all [bug 1860331]
Affects: fedora-all [bug 1860330]

Comment 2 Joshua Padman 2020-07-28 23:37:52 UTC
Created luajit tracking bugs for this issue:

Affects: openstack-rdo [bug 1861551]

Comment 8 Mark Cooper 2020-07-31 07:22:05 UTC
Statement:

OpenShift ServiceMesh proxy does package a vulnerable version of luajit. The segmentation fault is triggered via creating a inline code rule in the envoy filter, however envoy can also be caused to exit via a code rule which is also not syntactically correct either. A user who has permissions to change the filter rule can have the same affect regardless, hence this issue will not be addressed at this time and might be fixed in a future release.

Comment 9 Product Security DevOps Team 2020-07-31 07:27:41 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2020-15890


Note You need to log in before you can comment on or make changes to this bug.