Previously the length of the SM2 plaintext could be incorrectly calculated. The plaintext length was calculated by taking the ciphertext length and taking off an "overhead" value. The overhead value was assumed to have a "fixed" element of 10 bytes. This is incorrect since in some circumstances it can be more than 10 bytes. Additionally the overhead included the length of two integers C1x and C1y, which were assumed to be the same length as the field size (32 bytes for the SM2 curve). However in some cases these integers can have an additional padding byte when the msb is set, to disambiguate them from negative integers. Additionally the integers can also be less than 32 bytes in length in some cases. If the calculated overhead is incorrect and larger than the actual value this can result in the calculated plaintext length being too small. Applications are likely to allocate buffer sizes based on this and therefore a buffer overrun can occur. CVE-2021-3711 Issue reported by John Ouyang. Reviewed-by: Paul Dale <email@example.com> Reviewed-by: Nicola Tuveri <firstname.lastname@example.org>
|1 year ago|
|.github||2 years ago|
|Configurations||2 years ago|
|VMS||2 years ago|
|apps||1 year ago|
|crypto||1 year ago|
|demos||2 years ago|
|dev||2 years ago|
|doc||1 year ago|
|engines||2 years ago|
|external/perl||3 years ago|
|fuzz||1 year ago|
|gost-engine@62583fb222||2 years ago|
|include||1 year ago|
|krb5@aa9b4a2a64||2 years ago|
|ms||2 years ago|
|os-dep||7 years ago|
|providers||1 year ago|
|pyca-cryptography@0034926f2c||2 years ago|
|ssl||1 year ago|
|test||1 year ago|
|tools||2 years ago|
|util||1 year ago|
|wycheproof@2196000605||2 years ago|
|.gitattributes||2 years ago|
|.gitignore||2 years ago|
|.gitmodules||2 years ago|
|ACKNOWLEDGEMENTS.md||3 years ago|
|AUTHORS.md||2 years ago|
|CHANGES.md||2 years ago|
|CONTRIBUTING.md||2 years ago|
|Configure||1 year ago|
|FAQ.md||3 years ago|
|HACKING.md||3 years ago|
|INSTALL.md||1 year ago|
|LICENSE.txt||3 years ago|
|NEWS.md||2 years ago|
|NOTES-ANDROID.md||2 years ago|
|NOTES-DJGPP.md||2 years ago|
|NOTES-NONSTOP.md||2 years ago|
|NOTES-PERL.md||2 years ago|
|NOTES-UNIX.md||1 year ago|
|NOTES-VALGRIND.md||2 years ago|
|NOTES-VMS.md||2 years ago|
|NOTES-WINDOWS.md||2 years ago|
|README-ENGINES.md||2 years ago|
|README-FIPS.md||2 years ago|
|README-PROVIDERS.md||2 years ago|
|README.md||2 years ago|
|SUPPORT.md||2 years ago|
|VERSION.dat||2 years ago|
|appveyor.yml||2 years ago|
|build.info||2 years ago|
|config||3 years ago|
|config.com||3 years ago|
|configdata.pm.in||2 years ago|
|e_os.h||2 years ago|
Welcome to the OpenSSL Project
OpenSSL is a robust, commercial-grade, full-featured Open Source Toolkit for the Transport Layer Security (TLS) protocol formerly known as the Secure Sockets Layer (SSL) protocol. The protocol implementation is based on a full-strength general purpose cryptographic library, which can also be used stand-alone.
OpenSSL is descended from the SSLeay library developed by Eric A. Young and Tim J. Hudson.
The official Home Page of the OpenSSL Project is www.openssl.org.
Table of Contents
The OpenSSL toolkit includes:
libssl an implementation of all TLS protocol versions up to TLSv1.3 (RFC 8446).
libcrypto a full-strength general purpose cryptographic library. It constitutes the basis of the TLS implementation, but can also be used independently.
openssl the OpenSSL command line tool, a swiss army knife for cryptographic tasks, testing and analyzing. It can be used for
- creation of key parameters
- creation of X.509 certificates, CSRs and CRLs
- calculation of message digests
- encryption and decryption
- SSL/TLS client and server tests
- handling of S/MIME signed or encrypted mail
- and more...
For Production Use
Source code tarballs of the official releases can be downloaded from www.openssl.org/source. The OpenSSL project does not distribute the toolkit in binary form.
However, for a large variety of operating systems precompiled versions of the OpenSSL toolkit are available. In particular on Linux and other Unix operating systems it is normally recommended to link against the precompiled shared libraries provided by the distributor or vendor.
For Testing and Development
Although testing and development could in theory also be done using the source tarballs, having a local copy of the git repository with the entire project history gives you much more insight into the code base.
The official OpenSSL Git Repository is located at git.openssl.org. There is a GitHub mirror of the repository at github.com/openssl/openssl, which is updated automatically from the former on every commit.
A local copy of the Git Repository can be obtained by cloning it from the original OpenSSL repository using
git clone git://git.openssl.org/openssl.git
or from the GitHub mirror using
git clone https://github.com/openssl/openssl.git
If you intend to contribute to OpenSSL, either to fix bugs or contribute new features, you need to fork the OpenSSL repository openssl/openssl on GitHub and clone your public fork instead.
git clone https://github.com/yourname/openssl.git
This is necessary, because all development of OpenSSL nowadays is done via GitHub pull requests. For more details, see Contributing.
Build and Install
After obtaining the Source, have a look at the INSTALL file for detailed instructions about building and installing OpenSSL. For some platforms, the installation instructions are amended by a platform specific document.
- Notes for UNIX-like platforms
- Notes for Android platforms
- Notes for Windows platforms
- Notes for the DOS platform with DJGPP
- Notes for the OpenVMS platform
- Notes on Perl
- Notes on Valgrind
Specific notes on upgrading to OpenSSL 3.0 from previous versions, as well as known issues are available on the OpenSSL 3.0 Wiki page.
The manual pages for the master branch and all current stable releases are available online.
There is a Wiki at wiki.openssl.org which is currently not very active. It contains a lot of useful information, not all of which is up to date.
OpenSSL is licensed under the Apache License 2.0, which means that you are free to get and use it for commercial and non-commercial purposes as long as you fulfill its conditions.
See the LICENSE.txt file for more details.
There are various ways to get in touch. The correct channel depends on your requirement. see the SUPPORT file for more details.
If you are interested and willing to contribute to the OpenSSL project, please take a look at the CONTRIBUTING file.
A number of nations restrict the use or export of cryptography. If you are potentially subject to such restrictions you should seek legal advice before attempting to develop or distribute cryptographic code.
Copyright (c) 1998-2021 The OpenSSL Project
Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson
All rights reserved.