OpenSC Security Advisory [26-Feb-2009] CVE-2009-0368
OpenSC stores private data without proper access restrictions.
User "b.badrignans" reported this security problem on December 4th, 2008.
In June 2007 support form private data objects was added to OpenSC. Only later
a severe security bug was found out: while the OpenSC PKCS#11 implementation
requires PIN verification to access the data, low level APDU commands or
debugging tools like opensc-explorer or opensc-tool can access the private
data without any authentication. This was fixed in OpenSC 0.11.7.
RSA keys are not affected by this security problem. National eID cards and
other cards initialised by other software are not affected by this problem.
Only blank cards initialised with OpenSC are affected by this problem. It is
not known if the problem is limited to some drivers, but we believe all
drivers are affected. We could only test very few cards, but all of them had
the problem, and the fix worked on all of them. All other cards are completely
untested for either.
This fix only improves creating new private data objects. Cards already
initialised with such private data objects need to be modified to repair the
access control conditions on such cards. One way to do that is to erase the
card and re-initialise it, but doing this you would loose all content on the
card, including RSA private keys. An alternative is to download the private
data object(s) to your PC, delete them on the card, and store them once more
on the card with the new, fixed version of OpenSC. This procedure has been
tested with success on some cards, but no guaranty of any kind can be given.
opensc-0.11.7.ebuild target "alpha amd64 arm hppa ia64 m68k ppc ppc64 s390 sh sparc x86"
if you don't have smartcards I don't either. there have been numerous reports of this package working and I reasonably trust the upstream devs.
OpenSC before 0.11.7 allows physically proximate attackers to bypass
intended PIN requirements and read private data objects via a (1) low
level APDU command or (2) debugging tool, as demonstrated by reading
the 4601 or 4701 file with the opensc-explorer or opensc-tool program.
glsa vote: YES
Yes, too. Request filed.
dev-libs/opensc-0.11.8 has been stabilized on m68k due to bug #269920.
GLSA 200908-01, thanks everyone.