#1676 CoolKey Javacard applet integer overflow error
Closed: migrated by dmoluguw. Opened by jmagne.

The CoolKey Javacard applet used by the SC650 Smart Card contains an Integer
Overflow Error. The vulnerability is persistent in the most recent version
currently hosted online at http://svn.fedorahosted.org/svn/coolkey

Specifically, there is an unhandled integer overflow error within the
ReadObject() method in the cardedge.java file of the CoolKey package. Two short
integer variables 'offset' and 'size' may be considered tainted inputs from the
host machine, and specially chosen values of 'offset' and 'size' allow passage
through all of the exception handling to allow execution of the sendData()
method with an improperly chosen offset.


Per CS/DS meeting of 11/02/2015: 10.3

Have the simple one line fix for the applet compiled.

Completed a gpshell script to test the fix with the old and fixed applet to view the difference in behavior.

Have run the tests on an enrolled card and it works as expect.

Now need a quick review by BobR and a build before the new applet can be checked into TPS.

Per PKI Bug Council of 06/23/2016: 10.4

Metadata Update from @jmagne:
- Issue assigned to jmagne
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.4 (was: UNTRIAGED)

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 10.4)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2235

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

Metadata