Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1410074 - (CVE-2016-10109) CVE-2016-10109 pcsc-lite: Use-after-free of cardsList due to SCardReleaseContext invocations
CVE-2016-10109 pcsc-lite: Use-after-free of cardsList due to SCardReleaseCont...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20161230,repor...
: Security
Depends On: 1410075
Blocks: 1410078
  Show dependency treegraph
 
Reported: 2017-01-04 07:02 EST by Andrej Nemec
Modified: 2017-01-05 01:31 EST (History)
5 users (show)

See Also:
Fixed In Version: pcsc-lite 1.8.20
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)

  None (edit)
Description Andrej Nemec 2017-01-04 07:02:47 EST
A vulnerability was found in PCSC-Lite.  The SCardReleaseContext function normally releases resources associated with the given handle (including "cardsList") and clients should cease using this handle. A malicious client can however make the daemon invoke SCardReleaseContext and continue issuing other commands that use "cardsList", resulting in a use-after-free.  When SCardReleaseContext is invoked multiple times, it additionally results in a double-free of "cardsList".

References:

http://seclists.org/oss-sec/2017/q1/18
http://lists.alioth.debian.org/pipermail/pcsclite-muscle/Week-of-Mon-20161226/000779.html

Upstream patch:

https://anonscm.debian.org/cgit/pcsclite/PCSC.git/commit/?id=697fe05967af7ea215bcd5d5774be587780c9e22
Comment 1 Andrej Nemec 2017-01-04 07:06:44 EST
Created pcsc-lite tracking bugs for this issue:

Affects: fedora-all [bug 1410075]

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