Open x509-name-testing opened 1 year ago
I'll try to take a look at this within the next few days. I'm doing https://www.indigoalpineguides.com/alpine-cliff-camping this evening and need to prep for that.
https://github.com/phpseclib/phpseclib/commit/6cd6e8ceab9f2b55c8cd81d2192bf98cbeaf4627 should fix this.
Thanks!
Thanks
On Tue, Sep 26, 2023 at 12:07 AM terrafrost @.***> wrote:
6cd6e8c https://github.com/phpseclib/phpseclib/commit/6cd6e8ceab9f2b55c8cd81d2192bf98cbeaf4627 should fix this.
Thanks!
— Reply to this email directly, view it on GitHub https://github.com/phpseclib/phpseclib/issues/1943#issuecomment-1734052709, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCP22BXO2RIDO2CWSIQSD4TX4GT35ANCNFSM6AAAAAA476PLEU . You are receiving this because you authored the thread.Message ID: @.***>
Dear Seclib Team,
Can I get the CVE numbers for the hostname verification issue? It would be helpful for me to get a CVE assigned. And if you could help me with that would be much better. Many thanks, and looking forward to your reply and comments.
Regards, x509 Name Testing
I don't know how to create a CVE. All the CVE's that have been created for this project were done by Tidelift. The README.md says this of submitting security vulnerabilities:
To report a security vulnerability, please use the Tidelift security contact. Tidelift will coordinate the fix and disclosure.
https://github.com/phpseclib/phpseclib?tab=readme-ov-file#security-contact-information
The "Tidelift security contact" link, in turn, says to email security@tidelift.com.
Even if I did know how to create CVE's I still like the process as an independent and more objective third party is deciding whether or not something merits a CVE.
If one is desired I suppose I can begin researching how to create one sometime this week. Or I can email them to see if they can retroactively create one or some such (I've never done that before either; it's always been people emailing them).
Thanks for your reply. Could you please help me to connect with the Tidelift security team? I emailed the address before but failed (it seems I was blocked? not very sure). It would also be okay if you could help me create a CVE. Many thanks in advance.
Did you get a bounce back or something? Send me your email to terrafrost@php.net and a copy of the error you got back and I'll send it their way!
Hi Terrafrost, I sent the email to you. Please check your mailbox. Thanks very much.
Got the email and forwarded it off. We'll see what we see!
On Mon, Jun 24, 2024, 9:59 AM x509-name-testing @.***> wrote:
Hi Terrafrost, I sent the email to you. Please check your mailbox. Thanks very much.
— Reply to this email directly, view it on GitHub https://github.com/phpseclib/phpseclib/issues/1943#issuecomment-2186785891, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABULSV4BIROV4IU5IOQEKDZJAX53AVCNFSM6AAAAAA476PLEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWG44DKOBZGE . You are receiving this because you commented.Message ID: @.***>
Hi there,
I am writing to report a bug in the X.509 hostname verification process, which might result in name confusion attacks.
My testing environment is php7/php8. Here are some example codes.
In the previous case, the
+
matcheda
, which should be an obvious name confusion. And here are other 2 cases for ur reference:From the cases, it seems some characters, such as
+
, can act as wildcards in thephpseclib
. If so, it should be a security issue. Could the developing team have a look at these cases? Many thanks.I am looking forward to your reply.
Regards.