ID CVE-2015-4680
Summary FreeRADIUS 2.2.x before 2.2.8 and 3.0.x before 3.0.9 does not properly check revocation of intermediate CA certificates.
Vulnerable Configurations
  • cpe:2.3:a:freeradius:freeradius:3.0.0
  • cpe:2.3:a:freeradius:freeradius:3.0.1
  • FreeRADIUS 3.0.2
  • FreeRADIUS 3.0.3
  • FreeRADIUS 3.0.4
  • FreeRADIUS 3.0.5
  • FreeRADIUS 3.0.6
  • FreeRADIUS 3.0.7
  • FreeRADIUS 3.0.8
  • FreeRADIUS 2.2.0
  • cpe:2.3:a:freeradius:freeradius:2.2.1
  • cpe:2.3:a:freeradius:freeradius:2.2.2
  • cpe:2.3:a:freeradius:freeradius:2.2.3
  • cpe:2.3:a:freeradius:freeradius:2.2.4
  • cpe:2.3:a:freeradius:freeradius:2.2.5
  • cpe:2.3:a:freeradius:freeradius:2.2.6
  • cpe:2.3:a:freeradius:freeradius:2.2.7
  • cpe:2.3:o:suse:linux_enterprise_server:12:sp1
  • cpe:2.3:o:suse:linux_enterprise_server:12:sp2
  • cpe:2.3:o:suse:linux_enterprise_server:12:sp2:-:-:-:-:raspberry_pi
  • cpe:2.3:o:suse:linux_enterprise_software_development_kit:12:sp1
  • cpe:2.3:o:suse:linux_enterprise_software_development_kit:12:sp2
Base: 5.0 (as of 11-04-2017 - 19:52)
  • Creating a Rogue Certificate Authority Certificate
    An attacker exploits a weakness in the MD5 hash algorithm (weak collision resistance) to generate a certificate signing request (CSR) that contains collision blocks in the "to be signed" part. The attacker specially crafts two different, but valid X.509 certificates that when hashed with the MD5 algorithm would yield the same value. The attacker then sends the CSR for one of the certificates to the Certification Authority which uses the MD5 hashing algorithm. That request is completely valid and the Certificate Authority issues an X.509 certificate to the attacker which is signed with its private key. An attacker then takes that signed blob and inserts it into another X.509 certificate that the attacker generated. Due to the MD5 collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the attackers' second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority. To make the attack more interesting, the second certificate could be not just a regular certificate, but rather itself a signing certificate. Thus the attacker is able to start their own Certification Authority that is anchored in its root of trust in the legitimate Certification Authority that has signed the attackers' first X.509 certificate. If the original Certificate Authority was accepted by default by browsers, so will now the Certificate Authority set up by the attacker and of course any certificates that it signs. So the attacker is now able to generate any SSL certificates to impersonate any web server, and the user's browser will not issue any warning to the victim. This can be used to compromise HTTPS communications and other types of systems where PKI and X.509 certificates may be used (e.g., VPN, IPSec) .
nessus via4
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SU-2017-1777-1.NASL
    description This update for freeradius-server fixes the following issues : - CVE-2017-9148: Disable OpenSSL's internal session cache to mitigate authentication bypass. (bnc#1041445) - CVE-2015-4680: Add a configuration option to allow checking of all intermediate certificates for revocations. (bnc#935573) The following non security issue was fixed : - Cannot create table radpostauth because of deprecated TIMESTAMP(14) syntax. (bsc#912873) Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-11-30
    plugin id 101229
    published 2017-07-05
    reporter Tenable
    title SUSE SLES11 Security Update : freeradius-server (SUSE-SU-2017:1777-1)
  • NASL family Debian Local Security Checks
    description Several issues were discovered in FreeRADIUS, a high-performance and highly configurable RADIUS server. CVE-2014-2015 A stack-based buffer overflow was found in the normify function in the rlm_pap module, which can be attacked by existing users to cause denial of service or other issues. CVE-2015-4680 It was discovered that freeradius failed to check revocation of intermediate CA certificates, thus accepting client certificates issued by revoked certificates from intermediate CAs. Note that to enable checking of intermediate CA certificates, it is necessary to enable the check_all_crl option of the EAP TLS section in eap.conf. This is only necessary for servers using certificates signed by intermediate CAs. Servers that use self-signed CAs are unaffected. CVE-2017-9148 The TLS session cache fails to reliably prevent resumption of an unauthenticated session, which allows remote attackers (such as malicious 802.1X supplicants) to bypass authentication via PEAP or TTLS. For Debian 7 'Wheezy', these problems have been fixed in version 2.1.12+dfsg-1.2+deb7u1. We recommend that you upgrade your freeradius packages. NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-07-09
    plugin id 100623
    published 2017-06-06
    reporter Tenable
    title Debian DLA-977-1 : freeradius security update
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SU-2017-0102-1.NASL
    description This update of freeradius-server fixes several issues. Security issue fixed : - CVE-2015-4680: Fixed Insufficent CRL application for intermediate certificates (bsc#935573) Non security issues fixed : - Allows FreeRadius Server to start on SUSE Linux Enterprise Server 12 SP2 systems by relaxing a too strict openssl version check. (bsc#1013311) - Fixed radclient error free() invalid pointer (bsc#911886) - Fixed failing rebuild of freeradius-server package (bsc#951404) Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-11-30
    plugin id 96404
    published 2017-01-11
    reporter Tenable
    title SUSE SLES12 Security Update : freeradius-server (SUSE-SU-2017:0102-1)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_379788F3290011E5A4A5002590263BF5.NASL
    description oCERT reports : The FreeRADIUS server relies on OpenSSL to perform certificate validation, including Certificate Revocation List (CRL) checks. The FreeRADIUS usage of OpenSSL, in CRL application, limits the checks to leaf certificates, therefore not detecting revocation of intermediate CA certificates. An unexpired client certificate, issued by an intermediate CA with a revoked certificate, is therefore accepted by FreeRADIUS. Specifically sets the X509_V_FLAG_CRL_CHECK flag for leaf certificate CRL checks, but does not use X509_V_FLAG_CRL_CHECK_ALL for CRL checks on the complete trust chain. The FreeRADIUS project advises that the recommended configuration is to use self-signed CAs for all EAP-TLS methods.
    last seen 2019-02-21
    modified 2018-12-19
    plugin id 84697
    published 2015-07-14
    reporter Tenable
    title FreeBSD : freeradius -- insufficient CRL application vulnerability (379788f3-2900-11e5-a4a5-002590263bf5)
refmap via4
bid 75327
bugtraq 20150622 [oCERT-2015-008] FreeRADIUS insufficent CRL application
sectrack 1032690
suse SUSE-SU-2017:0102
Last major update 12-04-2017 - 08:57
Published 05-04-2017 - 13:59
Last modified 09-10-2018 - 15:57
Back to Top