Bug 1860324 (CVE-2020-15890)

Summary:	CVE-2020-15890 luajit: out-of-bounds read because __gc handler frame traversal is mishandled
Product:	[Other] Security Response	Reporter:	Dhananjay Arunesh <darunesh>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	dbecker, igor.raits, jjoyce, jschluet, kbasil, kconner, lhh, lpeer, mburns, oliver, rcernich, sclewis, siddhesh, slinaber
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-31 07:27:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1860330, 1860331, 1861551
Bug Blocks:	1860329

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 5 Mark Cooper 2020-07-31 05:37:14 UTC

Upstream fix: https://github.com/LuaJIT/LuaJIT/commit/53f82e6e2e858a0a62fd1a2ff47e9866693382e6

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