October 23, 2019
OpenSC is prone to multiple denial-of-service vulnerabilities. An attacker can exploit this issue to cause denial-of-service conditions. OpenSC through version 0.19.0 and 0.20.x through 0.20.0-rc3 are vulnerable.
- Opensc-Project Opensc 0.10.0
- Opensc-Project Opensc 0.10.1
- Opensc-Project Opensc 0.11.0
- Opensc-Project Opensc 0.11.1
- Opensc-Project Opensc 0.11.2
- Opensc-Project Opensc 0.11.3
- Opensc-Project Opensc 0.11.4
- Opensc-Project Opensc 0.11.5
- Opensc-Project Opensc 0.19.0
- Opensc-Project Opensc 0.19.0-rc1
- Opensc-Project Opensc 0.20.0
- Opensc-Project Opensc 0.20.0-rc1
- Opensc-Project Opensc 0.20.0-rc3
- Opensc-Project Opensc 0.4.0
- Opensc-Project Opensc 0.5.0
- Opensc-Project Opensc 0.6.0
- Opensc-Project Opensc 0.6.1
- Opensc-Project Opensc 0.7.0
- Opensc-Project Opensc 0.8.0
- Opensc-Project Opensc 0.8.1
- Opensc-Project Opensc 0.9.2
- Opensc-Project Opensc 0.9.3
- Opensc-Project Opensc 0.9.4
- Opensc-Project Opensc 0.9.5
- Opensc-Project Opensc 0.9.6
Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This may indicate exploit attempts or activity that results from successful exploits.
Do not accept or execute files from untrusted or unknown sources.
To reduce the likelihood of successful exploits, never handle files that originate from unfamiliar or untrusted sources.
Updates are available. Please see the references or vendor advisory for more information.
- Github - cac1: Correctly handle the buffer limits
- Github - fixed UNKNOWN READ
- Github - OpenSC 0.20.0 Changelog
- OpenSC - OpenSC Homepage
- Bugs Chromium - opensc:fuzz_pkcs15_reader: Crash in parse_sec_attr_44
- Bugs Chromium - opensc:fuzz_pkcs15_reader: Crash in sc_transmit_apdu
- Github - pkcs15-prkey: Simplify cleaning memory after failure
The vendor reported these issues.
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.com.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and firstname.lastname@example.org are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.