安全编码实践
实施安全原则，防止跨站脚本攻击（XSS）和数据泄露等常见漏洞
安全编码实践 是 CoddyKit 上的免费 Browser Extensions Development (Chrome & Edge) 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Browser Extensions Development (Chrome & Edge) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Browser Extensions Development (Chrome & Edge) 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Why Security Matters for Extensions
Browser extensions operate with significant privileges, interacting closely with user data and browsing sessions. This makes secure coding practices absolutely critical.
Poor security can lead to serious vulnerabilities like Cross-Site Scripting (XSS) and data leakage, compromising user privacy and system integrity.
Understanding XSS Vulnerabilities
Cross-Site Scripting (XSS) occurs when an attacker injects malicious scripts into a trusted web application, or in our case, into your extension's UI or content scripts.
These scripts can steal sensitive data, hijack user sessions, or even deface websites, all within the context of your extension's permissions.
The Danger of `innerHTML`
One of the most common causes of XSS in web development, and thus in extensions, is using innerHTML with untrusted input.
If you take text directly from a user (e.g., from a form field, a URL parameter, or even a web page's content) and inject it into the DOM using innerHTML, any embedded scripts will execute.
Safe DOM Manipulation: `textContent`
To prevent XSS when displaying untrusted plain text, always use the textContent property instead of innerHTML.
textContent treats all input as raw text, preventing any HTML tags or scripts from being parsed and executed by the browser. It's your first line of defense.
Using `textContent` in Practice
Try running this simple JavaScript example. Notice how textContent safely renders the script as plain text, while innerHTML would dangerously attempt to execute it.
const userInput = "<script>alert('XSS!');</script>";
// Simulate a DOM element
const divSafe = { textContent: '' };
const divUnsafe = { innerHTML: '' };
// Safe way: Using textContent
divSafe.textContent = userInput;
console.log("Safe (textContent):", divSafe.textContent);
// Unsafe way: Using innerHTML (DO NOT DO THIS!)
divUnsafe.innerHTML = userInput;
console.log("Unsafe (innerHTML):", divUnsafe.innerHTML);Sanitizing HTML When Needed
What if you genuinely need to allow *some* HTML (like bold or italic) from user input? In these cases, textContent isn't enough.
You must use a robust, well-maintained HTML sanitization library (e.g., DOMPurify). These libraries parse HTML, remove malicious tags/attributes, and return safe HTML. Never build your own HTML sanitizer.
Avoiding Dynamic Code Execution
Functions like eval(), new Function(), setTimeout(string), and setInterval(string) execute JavaScript code from a string.
This is a significant security risk. If an attacker can control the string argument, they can execute arbitrary code within your extension's context, potentially bypassing other security measures.
Protecting Against Data Leakage
Data leakage occurs when sensitive user data is unintentionally or maliciously exposed to unauthorized third parties. This is a critical concern for extensions.
Be extremely cautious when sending data from your extension to external servers. Always verify the destination, use secure protocols (HTTPS), and encrypt sensitive information if necessary.
Principle of Least Privilege
When declaring permissions in your extension's manifest.json, always adhere to the Principle of Least Privilege.
Request only the absolute minimum permissions required for your extension's functionality. Overly broad permissions increase the attack surface and the potential for data leakage if your extension is compromised.
Security Best Practices Check
Which of the following are recommended secure coding practices for browser extensions?
Recap: Keeping Extensions Secure
You've learned crucial secure coding practices for building robust browser extensions:
- Sanitize All Input: Use
textContentfor plain text; use robust libraries like DOMPurify for HTML. - Avoid Dynamic Code: Never execute code from untrusted strings using functions like
eval(). - Least Privilege: Request only the essential permissions your extension needs.
- Prevent Data Leakage: Be cautious when transmitting user data, ensuring secure destinations and protocols.
By integrating these practices, you build more trustworthy extensions that protect user privacy and security.
常见问题解答
「安全编码实践」课时是免费的吗？
是的 — 「安全编码实践」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Browser Extensions Development (Chrome & Edge) 课程的其余内容，请升级到 CoddyKit PRO。 Browser Extensions Development (Chrome & Edge) 课程共包含 4 节课。
「安全编码实践」这节课中我会学到什么？
实施安全原则，防止跨站脚本攻击（XSS）和数据泄露等常见漏洞 你通过在浏览器中直接运行的动手代码来练习 Browser Extensions Development (Chrome & Edge)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Browser Extensions Development (Chrome & Edge) 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Browser Extensions Development (Chrome & Edge) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。
「安全编码实践」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Browser Extensions Development (Chrome & Edge) 课中编写并运行代码吗？
能。每节 Browser Extensions Development (Chrome & Edge) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。