Bug 1886554 (CVE-2020-8264)

Summary: CVE-2020-8264 rubygem-actionpack: possible XSS vulnerability in Action Pack in development mode
Product: [Other] Security Response Reporter: Guilherme de Almeida Suckevicz <gsuckevi>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: akarol, bbuckingham, bcourt, bkearney, bmidwood, btotty, dmetzger, gmccullo, gtanzill, hhudgeon, jaruga, jfrey, jhardy, lzap, mmccune, mo, nmoumoul, obarenbo, pvalena, rchan, rjerrido, roliveri, ruby-packagers-sig, simaishi, smallamp, sokeeffe, sseago, strzibny, vondruch, xlecauch
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in rubygem-actionpack. A XSS vulnerability in Action Pack's Actionable Exceptions middleware while the application server is in development mode is possible. The highest threat from this vulnerability is to data confidentiality and integrity.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-09 20:21:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1886555    

Description Guilherme de Almeida Suckevicz 2020-10-08 18:22:44 UTC
There is a possible XSS vulnerability in Action Pack while the application server is in development mode. This vulnerability is in the Actionable Exceptions middleware.


Comment 3 Yadnyawalk Tale 2020-10-09 18:20:16 UTC

Red Hat products ships rubygem-actionpack, however, those are supposed to be run in production mode. This issue only impacts development mode, therefore mentioned products are not affected by this flaw.

Comment 4 Yadnyawalk Tale 2020-10-09 18:20:20 UTC
External References:


Comment 5 Product Security DevOps Team 2020-10-09 20:21:12 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):