Forum Discussion
khiali_130513
Mar 07, 2014Nimbostratus
The remote server's SSL certificate has already expired - Plugin ID 15901
Hi Experts
We are running Nessus Scan against our F5 BIG-IP LTM devices and getting following alert:-
The remote server's SSL certificate has already expired - Plugin ID 15901
Now prob...
Cory_50405
Mar 07, 2014Noctilucent
It may be that Nessus is assuming an expired certificate if it receives a mismatch between the CN of the certificate and the URL it used to access the LTM. As long as your certificate on the interface is still valid (whether it's a custom certificate or a self-signed should not matter), then this is a false positive finding.
- Cory_50405Mar 10, 2014NoctilucentYou got a permission denied error because your syntax was trying to execute it. Your cat should be fine, except grep for HTTPD (all caps). It is case sensitive.
- khiali_130513Mar 10, 2014NimbostratusI mised up 2 questions, just updated the relevant one. Regardding this, we are accessing LTM via IP address only. No CN. How will I know if th ecertificate is valid on the interface or not. All I know that its expired.
- Cory_50405Mar 10, 2014NoctilucentCorrect. So the Nessus finding should only be a real finding if the certificate you have loaded on the management interface is actually expired. Otherwise, it's a false positive. Doesn't matter which CA (or self signed), since you accessing by IP address.
- khiali_130513Mar 11, 2014NimbostratusHere is the cert related information:- General Properties Name: server Certificate Subject(s): My Company Ltd Certificate Properties Expires Jan 16, 2013 Version 3 Serial Number XXXX Subject:- Common Name: Organization: My Company Ltd Division: Locality: xxx State Or Province: Country: xxx I am a bit confused here. Management certificate is expired for sure as shown above. Almost a year ago. so Scan result is good. Now since we are using IP address only to access the management interface, so we can ignore the requirement of renewing this certificate. Please correct me if I am wrong.
- Cory_50405Mar 11, 2014NoctilucentSo the certificate is expired. You need to apply a valid certificate to the interface to mitigate the finding of an expired certificate. However, it shouldn't matter whether you use a self-signed certificate or one from your trusted CA. This is because you are accessing the device by IP address, and SSL certificates are based on hostname. There will always be a mismatch if you access by IP address. But the finding is an expired certificate, so put a valid one on your management interface and this finding is resolved.
- khiali_130513Mar 24, 2014NimbostratusOK, so I have updated the System ›› Device Certificates ›› Device Certificate by simply using the renew tab which was quite simple. I observed that there are other certs which are also expired under same menu System ›› Device Certificates ›› Trusted Device Certificates Here is the detail. These certs were expired for almost last 3 years as well Name: client Certificate Subject(s) : dhcp-5, Company Certificate Properties Expires : Jan 10, 2010 Version : 3 Serial Number x:x:x:x:x:ba:85:33 Subject Common Name: dhcp-5 Organization: Company Division: 123 Locality: xxx State Or Province: xxx Country: -- Issuer Self
- Cory_50405Mar 24, 2014NoctilucentDid this resolve the scanning failure?
- khiali_130513Mar 25, 2014NimbostratusI am still waiting for the scan results. As soon as i`ll get them, i`ll update.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects