On Monday, February 27, 2017 at 4:05:09 PM UTC-5, Jakob Bohm wrote: > On 27/02/2017 01:53, Itzhak Daniel wrote: > > How those lines are parsed? what happens when a client reaches a > > whitespace? Will this allow 'vietnamairlines.com' to use 'owa', 'mail' and > > 'autodiscover' in their internal infrastructure? > > > > Programs don't parse the text lines from the crt.sh website. They > parse the clearly delimited binary (DER encoded) certificate. > > Looking at a more detailed dump of the actual certificate shows that > those are indeed spaces and not a parsing error by crt.sh though. > > I don't know if owa.m.vietnamairlines.com ever existed, but I happen to > know that GlobalSign provides the 3 exchange-related DNS SANs at no > extra charge when ordering an EV certificate, so maybe those invalid > DNS SAN entries were simply never used or discovered. > > From all of this, it looks like a technical processing error when > generating the SAN attribute, as the primary name > (m.vietnamairlines.com) was emitted correctly. The certificate is > *currently* used by https://m.vietnamairlines.com and may never have > been intended (by the airline) for use with the 3 exchange names that > were incorrectly encoded (such as owa.m.vietnamairlines.com, not > owa.vietnamairlines.com). > > But really, GlobalSign should reach out to the airline and reissue the > certificate without the stray space characters, then revoke the broken > cert after the webserver has switched (within reasonable time).
Yes, we're working to do just this now. > GlobalSign should also check if other EV certificates were issued with > the same processing bug and arrange to have any such certificates > similarly fixed. > > Enjoy > > Jakob > -- > Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com > Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 > This public discussion message is non-binding and may contain errors. > WiseMo - Remote Service Management for PCs, Phones and Embedded _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy

