3 ms·
It misses the security considerations for names. Almost nobody knows about nor implements that. Eg for filenames or variable names.
by rurban 6y ago
It misses the security considerations for names. Almost nobody knows about nor implements that. Eg for filenames or variable names.
- pacaro 6y agoIf you're interested in this... https://en.wikipedia.org/wiki/Homoglyph https://en.wikipedia.org/wiki/Homoglyph
- jermier 6y agoAlso recently spotted as an avenue for attack in the wild: Magecart group uses homoglyph attacks to fool you into visiting malicious websites: https://www.zdnet.com/article/magecart-group-uses-homoglyph-attacks-to-fool-you-into-visiting-malicious-websites/ https://www.zdnet.com/article/magecart-group-uses-homoglyph-... Homoglyph attacks used in phishing campaign and Magecart attacks https://securityaffairs.co/wordpress/106916/hacking/homoglyph-attacks-phishing-campaign.html https://securityaffairs.co/wordpress/106916/hacking/homoglyp... https://cisomag.eccouncil.org/homoglyph-attacks/ https://cisomag.eccouncil.org/homoglyph-attacks/
- rurban 6y agoYou can easily avoid homoglyph attacks or similar stuff by following the relevant unicode security considerations. I'm on Moderately Restrictive level for General Security Profile for identifiers. http://perl11.org/blog/unicode-identifiers.html http://perl11.org/blog/unicode-identifiers.html Forbidding mixed scripts fixes this attack. You also need to normalized names, and a few more minor things.