Bug 1902139 (CVE-2019-8790) - CVE-2019-8790 swift: updating incorrect URLSession file descriptors management logic leads to information disclosure
Summary: CVE-2019-8790 swift: updating incorrect URLSession file descriptors managemen...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2019-8790
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: 1902140 1902987 1902988
Blocks: 1902141
TreeView+ depends on / blocked
 
Reported: 2020-11-27 04:34 UTC by Dhananjay Arunesh
Modified: 2020-12-02 15:23 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-12-01 05:33:52 UTC
Embargoed:

Attachments (Terms of Use)

Description Dhananjay Arunesh 2020-11-27 04:34:16 UTC 
This issue was addresses by updating incorrect URLSession file descriptors management logic to match Swift 5.0. This issue is fixed in Swift 5.1.1 for Ubuntu. Incorrect management of file descriptors in URLSession could lead to inadvertent data disclosure.

References:
https://support.apple.com/en-us/HT210647
Comment 1 Dhananjay Arunesh 2020-11-27 04:34:55 UTC 
Created swift tracking bugs for this issue:

Affects: epel-6 [bug 1902140]
Comment 2 Doran Moppert 2020-12-01 03:37:46 UTC 
Created swift-lang tracking bugs for this issue:

Affects: epel-8 [bug 1902987]
Affects: fedora-all [bug 1902988]
Comment 3 Ron Olson 2020-12-01 03:46:07 UTC 
Swift 5.3.1 is the currently-available version. Is this bug report still valid?
Comment 4 Product Security DevOps Team 2020-12-01 05:33:52 UTC 
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Comment 5 Dhananjay Arunesh 2020-12-02 15:23:59 UTC 
In reply to comment #3:
> Swift 5.3.1 is the currently-available version. Is this bug report still
> valid?

Hi,

yes this is a reported vulnerability with cve so we need to file the flaw for the vulnerable component which we ship either in our enterprise or community projects.
Note You need to log in before you can comment on or make changes to this bug.