FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The last vuln.xml file processed by FreshPorts is:

nothing found there

List all Vulnerabilities, by package

List all Vulnerabilities, by date

These are the vulnerabilities relating to the commit you have selected:

VuXML IDDescription
88dfd92f-3b9c-11eb-929d-d4c9ef517024LibreSSL -- NULL pointer dereference

The LibreSSL project reports:

Malformed ASN.1 in a certificate revocation list or a timestamp response token can lead to a NULL pointer dereference.

Discovery 2020-12-08
Entry 2020-12-11
Modified 2020-12-12
gt 3.2.0 lt 3.2.3

lt 3.1.5

lt 3.3.1
ea05c456-a4fd-11ec-90de-1c697aa5a594OpenSSL -- Infinite loop in BN_mod_sqrt parsing certificates

The OpenSSL project reports:

Infinite loop in BN_mod_sqrt() reachable when parsing certificates (High)

The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli.

Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form.

It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters.

Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters.

Thus vulnerable situations include:

  • TLS clients consuming server certificates
  • TLS servers consuming client certificates
  • Hosting providers taking certificates or private keys from customers
  • Certificate authorities parsing certification requests from subscribers
  • Anything else which parses ASN.1 elliptic curve parameters

Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue.

Discovery 2022-03-15
Entry 2022-03-16
Modified 2022-03-16
lt 1.1.1n,1

lt 3.0.2

lt 3.0.2

lt 3.4.3

lt 3.5.1

ge 13.0 lt 13.0_8

ge 12.3 lt 12.3_3

ge 12.2 lt 12.2_14

7caebe30-d7f1-11e6-a9a5-b499baebfeafopenssl -- timing attack vulnerability

Cesar Pereida Garcia reports:

The signing function in crypto/ecdsa/ecdsa_ossl.c in certain OpenSSL versions and forks is vulnerable to timing attacks when signing with the standardized elliptic curve P-256 despite featuring constant-time curve operations and modular inversion. A software defect omits setting the BN_FLG_CONSTTIME flag for nonces, failing to take a secure code path in the BN_mod_inverse method and therefore resulting in a cache-timing attack vulnerability.

A malicious user with local access can recover ECDSA P-256 private keys.

Discovery 2017-01-10
Entry 2017-01-11
Modified 2017-01-11
lt 1.0.2

lt 2.4.4_1

lt 2.5.0_1
91a337d8-83ed-11e6-bf52-b499baebfeafOpenSSL -- multiple vulnerabilities

OpenSSL reports:

Critical vulnerability in OpenSSL 1.1.0a

Fix Use After Free for large message sizes (CVE-2016-6309)

Moderate vulnerability in OpenSSL 1.0.2i

Missing CRL sanity check (CVE-2016-7052)

Discovery 2016-09-26
Entry 2016-09-26
Modified 2016-10-10
lt 1.0.2j,1

lt 1.1.0b

lt 2.4.3

lt 2.4.3

ge 11.0 lt 11.0_1
6f0529e2-2e82-11e6-b2ec-b499baebfeafOpenSSL -- vulnerability in DSA signing

The OpenSSL team reports:

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. This has been demonstrated through a cache-timing attack to be sufficient for an attacker to recover the private DSA key.

Discovery 2016-06-09
Entry 2016-06-09
Modified 2016-12-20
lt 1.0.2_13

lt 2.2.9

ge 2.3.0 lt 2.3.6

lt 2.4.1;a=commit;h=399944622df7bd81af62e67ea967c470534090e2
c82ecac5-6e3f-11e8-8777-b499baebfeafOpenSSL -- Client DoS due to large DH parameter

The OpenSSL project reports:

During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished. This could be exploited in a Denial Of Service attack.

Discovery 2018-06-12
Entry 2018-06-12
Modified 2018-07-24
lt 2.6.5

ge 2.7.0 lt 2.7.4

lt 1.0.2o_4,1

lt 1.1.0h_2