<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl, branch OpenSSL_1_0_2h</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_0_2h</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_0_2h'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2016-05-03T13:46:41Z</updated>
<entry>
<title>Prepare for 1.0.2h release</title>
<updated>2016-05-03T13:46:41Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2016-05-03T13:46:41Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=5dd94f1847c744929a3bd24819f1c99644bb18c7'/>
<id>urn:sha1:5dd94f1847c744929a3bd24819f1c99644bb18c7</id>
<content type='text'>
Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
</content>
</entry>
<entry>
<title>make update</title>
<updated>2016-05-03T13:46:41Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2016-05-03T13:46:41Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=76564c8e7865ef45aa45d44d4d99979f181f8a74'/>
<id>urn:sha1:76564c8e7865ef45aa45d44d4d99979f181f8a74</id>
<content type='text'>
Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
</content>
</entry>
<entry>
<title>Update CHANGES and NEWS for the new release</title>
<updated>2016-05-03T12:19:10Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2016-05-03T08:37:23Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=b4d56b8ecb985ed8c8d3b757b5a728aa52143e41'/>
<id>urn:sha1:b4d56b8ecb985ed8c8d3b757b5a728aa52143e41</id>
<content type='text'>
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
</content>
</entry>
<entry>
<title>Fix ASN1_INTEGER handling.</title>
<updated>2016-05-03T12:05:34Z</updated>
<author>
<name>Dr. Stephen Henson</name>
<email>steve@openssl.org</email>
</author>
<published>2016-04-15T01:37:09Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=d4b25980020821d4685752ecb9105c0902109ab5'/>
<id>urn:sha1:d4b25980020821d4685752ecb9105c0902109ab5</id>
<content type='text'>
Only treat an ASN1_ANY type as an integer if it has the V_ASN1_INTEGER
tag: V_ASN1_NEG_INTEGER is an internal only value which is never used
for on the wire encoding.

Thanks to David Benjamin &lt;davidben@google.com&gt; for reporting this bug.

This was found using libFuzzer.

RT#4364 (part)CVE-2016-2108.

Reviewed-by: Emilia Käsper &lt;emilia@openssl.org&gt;
</content>
</entry>
<entry>
<title>Check that we have enough padding characters.</title>
<updated>2016-05-03T12:05:34Z</updated>
<author>
<name>Kurt Roeckx</name>
<email>kurt@roeckx.be</email>
</author>
<published>2016-04-16T21:08:56Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=68595c0c2886e7942a14f98c17a55a88afb6c292'/>
<id>urn:sha1:68595c0c2886e7942a14f98c17a55a88afb6c292</id>
<content type='text'>
Reviewed-by: Emilia Käsper &lt;emilia@openssl.org&gt;

CVE-2016-2107

MR: #2572
</content>
</entry>
<entry>
<title>Remove some documentation for functions not in 1.0.x</title>
<updated>2016-05-03T11:53:47Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2016-05-03T11:45:45Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=643e8e972e54fa358935e5f8b7f5a8be9616d56b'/>
<id>urn:sha1:643e8e972e54fa358935e5f8b7f5a8be9616d56b</id>
<content type='text'>
A few functions in the recently added EVP_EncodeInit docs don't apply to
the 1.0.x branches.

Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
</content>
</entry>
<entry>
<title>Add documentation for EVP_EncodeInit() and similar functions</title>
<updated>2016-05-03T10:50:13Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2016-04-25T10:54:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=0b3762a342bef77fcd8c2d712eae4860af706b20'/>
<id>urn:sha1:0b3762a342bef77fcd8c2d712eae4860af706b20</id>
<content type='text'>
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
</content>
</entry>
<entry>
<title>Ensure EVP_EncodeUpdate handles an output length that is too long</title>
<updated>2016-05-03T10:49:12Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2016-04-25T08:06:29Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=3850c2b9d55fb91ea1d9b8228fd8a761d0ba1780'/>
<id>urn:sha1:3850c2b9d55fb91ea1d9b8228fd8a761d0ba1780</id>
<content type='text'>
With the EVP_EncodeUpdate function it is the caller's responsibility to
determine how big the output buffer should be. The function writes the
amount actually used to |*outl|. However this could go negative with a
sufficiently large value for |inl|. We add a check for this error
condition.

Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
</content>
</entry>
<entry>
<title>Avoid overflow in EVP_EncodeUpdate</title>
<updated>2016-05-03T10:48:28Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2016-03-04T10:17:17Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=172c6e1e14defe7d49d62f5fc9ea6a79b225424f'/>
<id>urn:sha1:172c6e1e14defe7d49d62f5fc9ea6a79b225424f</id>
<content type='text'>
An overflow can occur in the EVP_EncodeUpdate function which is used for
Base64 encoding of binary data. If an attacker is able to supply very large
amounts of input data then a length check can overflow resulting in a heap
corruption. Due to the very large amounts of data involved this will most
likely result in a crash.

Internally to OpenSSL the EVP_EncodeUpdate function is primarly used by the
PEM_write_bio* family of functions. These are mainly used within the
OpenSSL command line applications, so any application which processes
data from an untrusted source and outputs it as a PEM file should be
considered vulnerable to this issue.

User applications that call these APIs directly with large amounts of
untrusted data may also be vulnerable.

Issue reported by Guido Vranken.

CVE-2016-2105

Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
</content>
</entry>
<entry>
<title>Prevent EBCDIC overread for very long strings</title>
<updated>2016-05-03T09:25:05Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2016-04-28T09:46:55Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=9f2ccf1d718ab66c778a623f9aed3cddf17503a2'/>
<id>urn:sha1:9f2ccf1d718ab66c778a623f9aed3cddf17503a2</id>
<content type='text'>
ASN1 Strings that are over 1024 bytes can cause an overread in
applications using the X509_NAME_oneline() function on EBCDIC systems.
This could result in arbitrary stack data being returned in the buffer.

Issue reported by Guido Vranken.

CVE-2016-2176

Reviewed-by: Andy Polyakov &lt;appro@openssl.org&gt;
</content>
</entry>
</feed>
