目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

目标: 1000 元 · 已筹: 1000 元

100.0%
请我们喝杯咖啡

CWE-79 在Web页面生成时对输入的转义处理不恰当(跨站脚本) 类漏洞列表 21787

CWE-79 在Web页面生成时对输入的转义处理不恰当(跨站脚本) 类弱点 21787 条 CVE 漏洞汇总，含 AI 中文分析。

CWE-79 即跨站脚本攻击，属于输入验证类漏洞。攻击者通过在网页中注入恶意脚本，利用服务器未正确过滤用户输入的特性，使受害者在浏览器中执行非预期代码，从而窃取会话令牌或篡改页面内容。开发者应避免此类风险，需严格对用户输入进行白名单验证，并在输出到 HTML 时实施上下文相关的编码与转义，确保危险字符被正确中和。

MITRE CWE 官方描述
CWE：CWE-79 在生成网页时未正确中和输入（'跨站脚本攻击' Cross-site Scripting） 产品在将用户可控输入放入用于向其他用户提供的网页输出之前，未对其进行中和或中和不当。 跨站脚本攻击存在多种变体，其特征是使用了不同的术语或涉及不同的攻击拓扑结构。然而，它们都指向同一个根本性弱点：在攻击者与受害者之间，对危险输入未进行正确的中和处理。
常见影响 (3)
Access Control, ConfidentialityBypass Protection Mechanism, Read Application Data
The most common attack performed with cross-site scripting involves the disclosure of private information stored in user cookies, such as session information. Typically, a malicious user will craft a client-side script, which -- when parsed by a web browser -- performs some activity on behalf of the…
Integrity, Confidentiality, AvailabilityExecute Unauthorized Code or Commands
In some circumstances it may be possible to run arbitrary code on a victim's computer when cross-site scripting is combined with other flaws, for example, "drive-by hacking."
Confidentiality, Integrity, Availability, Access ControlExecute Unauthorized Code or Commands, Bypass Protection Mechanism, Read Application Data
The consequence of an XSS attack is the same regardless of whether it is stored or reflected. The difference is in how the payload arrives at the server. XSS can cause a variety of problems for the end user that range in severity from an annoyance to complete account compromise. Some cross-site scri…
缓解措施 (5)
Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
Implementation, Architecture and DesignUnderstand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required e…
Architecture and Design, ImplementationUnderstand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly throug…
Effectiveness: Limited
Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Architecture and DesignIf available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
代码示例 (2)
The following code displays a welcome message on a web page based on the HTTP GET username parameter (covers a Reflected XSS (Type 1) scenario).
$username = $_GET['username']; echo '<div class="header"> Welcome, ' . $username . '</div>';
Bad · PHP
http://trustedSite.example.com/welcome.php?username=<Script Language="Javascript">alert("You've been attacked!");</Script>
Attack
The following code displays a Reflected XSS (Type 1) scenario.
<% String eid = request.getParameter("eid"); %> ... Employee ID: <%= eid %>
Bad · JSP
<% protected System.Web.UI.WebControls.TextBox Login; protected System.Web.UI.WebControls.Label EmployeeID; ... EmployeeID.Text = Login.Text; %> <p><asp:label id="EmployeeID" runat="server" /></p>
Bad · ASP.NET
CVE ID标题CVSS风险等级Published
CVE-2014-5408 Nordex Control Wind Farm Portal 2 SCADA设备跨站脚本漏洞 — Nordex Control 2 (NC2) SCADA 6.1 -2014-11-05
CVE-2014-5411 Schneider Electric StruxureWare SCADA Expert ClearSCADA 跨站脚本漏洞 — ClearSCADA 5.4 -2014-09-18
CVE-2014-5397 Schneider Electric WIS Portal 跨站脚本漏洞 — Wonderware Information Server Portal 6.1 -2014-08-28
CVE-2014-2370 多款Omron产品跨站脚本漏洞 — NS15 5.4 -2014-07-24
CVE-2011-2920 Red Hat Network Satellite 跨站脚本漏洞 — Red Hat Enterprise Linux 6 5.5 Medium2014-02-05
CVE-2011-2927 Red Hat Network Satellite 跨站脚本漏洞 — Red Hat Enterprise Linux 6 5.4 Medium2014-02-05
CVE-2011-3344 Red Hat Network Satellite 跨站脚本漏洞 — Red Hat Enterprise Linux 6 5.4 Medium2014-02-05

CWE-79（在Web页面生成时对输入的转义处理不恰当(跨站脚本)） 是常见的弱点类别，本平台收录该类弱点关联的 21787 条 CVE 漏洞。