Checkout Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
update build config

    • -5
    • +0

update to 7.9p1

    • -1
    • +1
    • -10
    • +18
    • -0
    • +374
  1. … 363 more files in changeset.
openssl 1.0.2p

    • -55
    • +55
    • -5
    • +16
    • -24
    • +24
    • -0
    • +72
  1. … 806 more files in changeset.
Update OpenSSH to 7.5p1. This removes protocol 1

    • -2
    • +2
  1. … 666 more files in changeset.
add some files

    • -0
    • +15
    • -0
    • +209
    • -0
    • +62
    • -0
    • +218
    • -0
    • +60
    • -0
    • +17
fix merge issues

    • -1
    • +1
    • -181
    • +184
  1. … 157 more files in changeset.
remove more unneeded files

    • -0
    • +0
    • -100
    • +0
  1. … 140 more files in changeset.
remove unneeded files

  1. … 360 more files in changeset.
update to openssl 1.0.1u

    • -0
    • +0
  1. … 2508 more files in changeset.
set to null

    • -0
    • +0
    • -0
    • +0
    • -0
    • +0
  1. … 194 more files in changeset.
fix an impersonation attack against heimdal.

dont do that

update namespace

update defaults

patchup files

update config.h

OpenSSH 7.3p1

    • -7
    • +32
  1. … 467 more files in changeset.
Due to improper handling of alert packets, OpenSSL would consume an excessive

amount of CPU time processing undefined alert messages.

fix a regression from our last OpenSSL patch

OpenSSL security patch

A malicious client can send an excessively large OCSP Status Request extension.

If that client continually requests renegotiation, sending a large OCSP Status

Request extension each time, then there will be unbounded memory growth on the

server. [CVE-2016-6304]

An overflow can occur in MDC2_Update() either if called directly or through

the EVP_DigestUpdate() function using MDC2. If an attacker is able to supply

very large amounts of input data after a previous call to EVP_EncryptUpdate()

with a partial block then a length check can overflow resulting in a heap

corruption. [CVE-2016-6303]

If a server uses SHA512 for TLS session ticket HMAC it is vulnerable to a

DoS attack where a malformed ticket will result in an OOB read which will

ultimately crash. [CVE-2016-6302]

The function BN_bn2dec() does not check the return value of BN_div_word().

This can cause an OOB write if an application uses this function with an

overly large BIGNUM. This could be a problem if an overly large certificate

or CRL is printed out from an untrusted source. TLS is not affected because

record limits will reject an oversized certificate before it is parsed.


The function TS_OBJ_print_bio() misuses OBJ_obj2txt(): the return value is

the total length the OID text representation would use and not the amount

of data written. This will result in OOB reads when large OIDs are presented.


Some calculations of limits in OpenSSL have used undefined pointer arithmetic.

This could cause problems with some malloc implementations. [CVE-2016-2177]

Operations in the DSA signing algorithm should run in constant time in order to

avoid side channel attacks. A flaw in the OpenSSL DSA implementation means that

a non-constant time codepath is followed for certain operations. [CVE-2016-2178]

In a DTLS connection where handshake messages are delivered out-of-order those

messages that OpenSSL is not yet ready to process will be buffered for later

use. Under certain circumstances, a flaw in the logic means that those messages

do not get removed from the buffer even though the handshake has been completed.

An attacker could force up to approx. 15 messages to remain in the buffer when

they are no longer required. These messages will be cleared when the DTLS

connection is closed. The default maximum size for a message is 100k. Therefore

the attacker could force an additional 1500k to be consumed per connection.


A flaw in the DTLS replay attack protection mechanism means that records that

arrive for future epochs update the replay protection "window" before the MAC

for the record has been validated. This could be exploited by an attacker by

sending a record for the next epoch (which does not have to decrypt or have a

valid MAC), with a very large sequence number. This means that all subsequent

legitimate packets are dropped causing a denial of service for a specific

DTLS connection. [CVE-2016-2181]

In OpenSSL 1.0.2 and earlier some missing message length checks can result in

OOB reads of up to 2 bytes beyond an allocated buffer. There is a theoretical

DoS risk but this has not been observed in practice on common platforms.


alrightythen just drop the 0 case

OpenSSL security patch

The padding check in AES-NI CBC MAC was rewritten to be in constant time

by making sure that always the same bytes are read and compared against

either the MAC or padding bytes. But it no longer checked that there was

enough data to have both the MAC and padding bytes. [CVE-2016-2107]

An overflow can occur in the EVP_EncodeUpdate() function which is used for

Base64 encoding of binary data. [CVE-2016-2105]

An overflow can occur in the EVP_EncryptUpdate() function, however it is

believed that there can be no overflows in internal code due to this problem.


When ASN.1 data is read from a BIO using functions such as d2i_CMS_bio()

a short invalid encoding can casuse allocation of large amounts of memory

potentially consuming excessive resources or exhausting memory.


    • -0
    • +3
OpenSSH doesn't have the luck of the Irish.

Fix a security issue with OpenSSH X11 forwarding that can allow an attacker

run shell commands on the call to xauth.

  1. … 1 more file in changeset.
Security patch OpenSSL for DROWN

A cross-protocol attack was discovered that could lead to decryption of TLS

sessions by using a server supporting SSLv2 and EXPORT cipher suites as a

Bleichenbacher RSA padding oracle. Note that traffic between clients and

non-vulnerable servers can be decrypted provided another server supporting

SSLv2 and EXPORT ciphers (even with a different protocol such as SMTP, IMAP

or POP3) shares the RSA keys of the non-vulnerable server. This vulnerability

is known as DROWN. [CVE-2016-0800]

A double free bug was discovered when OpenSSL parses malformed DSA private

keys and could lead to a DoS attack or memory corruption for applications that

receive DSA private keys from untrusted sources. This scenario is considered

rare. [CVE-2016-0705]

The SRP user database lookup method SRP_VBASE_get_by_user had confusing memory

management semantics; the returned pointer was sometimes newly allocated, and

sometimes owned by the callee. The calling code has no way of distinguishing

these two cases. [CVE-2016-0798]

In the BN_hex2bn function, the number of hex digits is calculated using an int

value |i|. Later |bn_expand| is called with a value of |i * 4|. For large

values of |i| this can result in |bn_expand| not allocating any memory because

|i * 4| is negative. This can leave the internal BIGNUM data field as NULL

leading to a subsequent NULL pointer dereference. For very large values of

|i|, the calculation |i * 4| could be a positive value smaller than |i|. In

this case memory is allocated to the internal BIGNUM data field, but it is

insufficiently sized leading to heap corruption. A similar issue exists in

BN_dec2bn. This could have security consequences if BN_hex2bn/BN_dec2bn is

ever called by user applications with very large untrusted hex/dec data. This

is anticipated to be a rare occurrence. [CVE-2016-0797]

The internal |fmtstr| function used in processing a "%s" formatted string in

the BIO_*printf functions could overflow while calculating the length of

a string and cause an out-of-bounds read when printing very long strings.


A side-channel attack was found which makes use of cache-bank conflicts on the

Intel Sandy-Bridge microarchitecture which could lead to the recovery of RSA

keys. [CVE-2016-0702]

s2_srvr.c did not enforce that clear-key-length is 0 for non-export ciphers.

If clear-key bytes are present for these ciphers, they displace encrypted-key

bytes. [CVE-2016-0703]

s2_srvr.c overwrites the wrong bytes in the master key when applying

Bleichenbacher protection for export cipher suites. [CVE-2016-0704]

Obtained from: OpenSSL & FreeBSD

    • -197
    • +312
    • -10
    • +10
    • -1
    • +1
    • -71
    • +116
  1. … 1 more file in changeset.
OpenSSL CVE-2015-3197

A malicious client can negotiate SSLv2 ciphers that have been disabled on

the server and complete SSLv2 handshakes even if all SSLv2 ciphers have

been disabled, provided that the SSLv2 protocol was not also disabled via


disable roaming in the source code

turn off roaming

fix 3 security issues with OpenSSL

  1. … 1 more file in changeset.
A programming error in the privileged monitor process of the sshd(8)

service may allow the username of an already-authenticated user to be

overwritten by the unprivileged child process.

A use-after-free error in the privileged monitor process of he sshd(8)

service may be deterministically triggered by the actions of a

compromised unprivileged child process.

A use-after-free error in the session multiplexing code in the sshd(8)

service may result in unintended termination of the connection.