Cross-site scripting (XSS) vulnerabilities continue to appear in software, making it easy pickings for threat actors.

The catch is, though, cross-site scripting vulnerabilities are preventable and should not be present in software products.

Cross-site scripting vulnerabilities arise when manufacturers fail to properly validate, sanitize, or escape inputs, according to a Secure by Design alert issued by the Cybersecurity and Infrastructure Security Agency (CISA) and the FBI. These failures allow threat actors to inject malicious scripts into web applications, exploiting them to manipulate, steal, or misuse data across different contexts.

Although some developers employ input sanitization techniques to prevent XSS vulnerabilities, this approach is not infallible and should also end up reinforced with additional security measures.

To further prevent these vulnerabilities, technical leaders should:

Schneider Bold
  • Review their written threat models
  • Ensure software validates input for structure and meaning
  • Use modern web frameworks that offer easy-to-use functions for output encoding to ensure proper escaping or quoting
    — By distinguishing user input from application code, these frameworks make it so that the burden doesn’t fall on developers to correctly escape user input every time. Follow the framework’s guidance for preventing any remaining edge cases that may lead to XSS vulnerabilities.
    — When unable to use modern web frameworks, ensure that all user input displayed in web applications undergoes proper escaping or sanitization.
  • Conduct code reviews
  • Implement aggressive adversarial product testing to ensure the quality and security of their code throughout the development lifecycle

CISA and the FBI encourage users to follow these three principles:

1. Take Ownership of Customer Security Outcomes: Software manufacturers must prioritize customer security by eliminating cross-site scripting vulnerabilities from their products.

2. Embrace Radical Transparency and Accountability: Manufacturers should lead with transparency when disclosing product vulnerabilities. To that end, manufacturers should track the vulnerability associated with their products and disclose these to their customers via the CVE program.

3. Build Organizational Structure and Leadership to Achieve These Goals: Technology manufacturing executives should give the security of their products the same level of care they give to cost. Consider the full picture where customers, our economy, and our national security are currently bearing the brunt of business decisions to not build security into their products.

Click here for additional information on the Cross-Site Scripting vulnerabilities Secure by Design alert.

Pin It on Pinterest

Share This