-
Notifications
You must be signed in to change notification settings - Fork 581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] OpenSIPS does not verify hostnames in TLS certificates (?) #3064
Comments
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
Yes, there is progress here, 2 days ago I submitted a pull request, #3078 |
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
The bug still exists. |
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
Yes, the bug still exists. I have submitted an alternative implementation that does not require changing everywhere that touches sockaddr_union. |
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
Yes, the bug still exists. |
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
Yes, the bug still exists & I pushed another commit to my PR today. |
Hi @jes , thanks for the report and work here. I re-labeled this a feature and not bug, as the hostname verification is not a must, actually there are cases where you do not want to be done as may be impossible to have such a setup (it highly depends on what you are using the TLS for, the SIP scenario). Also, as per your patch, the check is optional, not mandatory. |
Great, thanks Bogdan :) - Looking forward to seeing TLS hostname verification in OpenSIPS. |
OpenSIPS version you are running
Describe the bug
When OpenSIPS connects to a TLS server that presents a certificate that does not match its hostname, OpenSIPS thinks the certificate passes validation and allows communication anyway.
There is probably a comparable bug regarding checking client certificates.
To Reproduce
Expected behavior
I expected OpenSIPS to reject a certificate when the common name (or subject alternate names) don't match the hostname it is trying to connect to.
Relevant System Logs
OS/environment information
Additional context
This probably means existing OpenSIPS installations are MITM-able by anyone who can get a valid certificate for any domain (which is everyone).
The text was updated successfully, but these errors were encountered: