sc_context_create in ctx.c in libopensc in OpenSC 0.19.0 has a memory leak, as demonstrated by a call from eidenv.
Weakness
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Opensc | Opensc_project | 0.19.0 (including) | 0.19.0 (including) |
| Opensc | Ubuntu | bionic | * |
| Opensc | Ubuntu | cosmic | * |
| Opensc | Ubuntu | disco | * |
| Opensc | Ubuntu | eoan | * |
| Opensc | Ubuntu | esm-apps/bionic | * |
| Opensc | Ubuntu | trusty | * |
| Opensc | Ubuntu | upstream | * |
| Opensc | Ubuntu | xenial | * |
Potential Mitigations
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
- For example, glibc in Linux provides protection against free of invalid pointers.
- When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
- To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.
References
- http://www.openwall.com/lists/oss-security/2019/12/29/1
- https://github.com/OpenSC/OpenSC/issues/1586
- https://lists.debian.org/debian-lts-announce/2023/06/msg00025.html
- http://www.openwall.com/lists/oss-security/2019/12/29/1
- https://github.com/OpenSC/OpenSC/issues/1586
- https://lists.debian.org/debian-lts-announce/2023/06/msg00025.html