Potential Vulnerability for X509 Certificate Verification
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nagios-plugins (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hostname verification is an important step when verifying X509 certificates, however, people tend to miss the step when using SSL/TLS, which might cause severe man in the middle attack and break the entire TLS mechanism.
We believe that nagios-
We found the vulnerability by static analysis, typically, a process of verification involves calling a chain of API, and we can deduce whether the communication process is vulnerable by detecting whether the process satisfies a certain relation.
The result format is like this:
notice: Line Number@Method Name, Source File
We provide this result to help developers to locate the problem faster.
This is the result for nagios-
[PDG]np_
[Found]
[HASH] 2965878942 [LineNo]@ 60[Kind]
[INFO] API SSL_new() Found! --> [HASH] 3737899610 [LineNo]@ 54[Kind]
[INFO] API SSL_CTX_new() Found! --> [HASH] 26244883 [LineNo]@ 50[Kind]
[INFO] API SSLv23_
[INFO] API SSL_get_
[Warning] No SSL_get_
We don't have a POC because we didn't succeed in configuring this software or don't know the way to verify the vulnerability. But through the analysis of the source code, we believe it breaks the ssl certificate verfication protocol.
for more information about the importance of checking hostname:
see http://
Thanks.
information type: | Private Security → Public Security |
information type: | Public Security → Public |
Right from the plugins documentation (--help) of the plugins:
Please note that this plugin does not check if the presented server
certificate matches the hostname of the server, or if the certificate
has a valid chain of trust to one of the locally installed CAs.
The question now is, how do you come to the conclusion, that the plugins "didn't check ... the expired date of the certificate."?