Potential Vulnerability for X509 Certificate Verification
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
spamassassin (Ubuntu) |
Expired
|
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 spamc didn't check whether the hostname matches the name in the ssl certificate.
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 spamc:
[PDG]message_filter
[Found]
[HASH] 3238387200 [LineNo]@ 1369[Kind]
[INFO] API SSL_new() Found! --> [HASH] 2841348688 [LineNo]@ 1367[Kind]
[INFO] API SSL_CTX_new() Found! --> [HASH] 1784966074 [LineNo]@ 1211[Kind]
[Warning] No secure SSL_Method API found! Potentially vulnerable!!!
[PDG]message_tell
[Found]
[HASH] 3756788397 [LineNo]@ 1717[Kind]
[INFO] API SSL_new() Found! --> [HASH] 894746177 [LineNo]@ 1715[Kind]
[INFO] API SSL_CTX_new() Found! --> [HASH] 1784966074 [LineNo]@ 1211[Kind]
[Warning] No secure SSL_Method API found! Potentially vulnerable!!!
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 |
description: | updated |
Thank you for reporting a bug in Ubuntu. Has this issue been files/forwarded upstream?