(punycode) homograph attacks with Κʻ / ĸ (U+0138, *Kra*)
Categories
(Core :: Networking, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: u543083, Assigned: jfkthame)
References
Details
(Keywords: csectype-spoof, sec-moderate, Whiteboard: [necko-backlog][adv-main68+])
Attachments
(2 files)
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
Comment 3•9 years ago
|
||
Updated•9 years ago
|
Comment 4•8 years ago
|
||
Updated•8 years ago
|
Comment 5•8 years ago
|
||
Comment 6•8 years ago
|
||
Comment 7•8 years ago
|
||
Comment 9•8 years ago
|
||
Comment 10•8 years ago
|
||
Comment 11•7 years ago
|
||
Comment 12•7 years ago
|
||
Updated•6 years ago
|
Comment 14•6 years ago
|
||
Jonathan: in comment 10 the Unicode folks told Gerv they were going to list this character, but I don't see that (the multitude of specifications and data files is confusing, though). In any case we're still supporting this character and it's pretty spoofy. Can we just go ahead and add it to netwerk/dns/IDNCharacterBlocklist.inc ?
Assignee | ||
Comment 15•6 years ago
|
||
Yes, I think that would be fine for now.
I sent a query about this to the Unicode technical committee, and it appears to have slipped through the cracks during UTS 39 revisions. By the time of Gerv's feedback, there had been substantial restructuring of the data, such that the file xidmodifications.txt and the category "historic" no longer existed, and it seems this was overlooked in the transition and updates.
I expect we can get this fixed upstream, but it'll take time to work through the process. Meanwhile, adding it to our blocklist would be the more immediate solution.
Assignee | ||
Comment 16•6 years ago
|
||
Comment 17•6 years ago
|
||
Comment 18•6 years ago
|
||
bugherder |
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Description
•