312-50V11 · Question #231
A company's Web development team has become aware of a certain type of security vulnerability in their Web software. To mitigate the possibility of this vulnerability being exploited, the team wants…
The correct answer is A. Cross-site scripting vulnerability. Allowing raw HTML input in a web application creates a cross-site scripting (XSS) vulnerability, enabling attackers to inject malicious scripts executed in other users' browsers.
Question
A company's Web development team has become aware of a certain type of security vulnerability in their Web software. To mitigate the possibility of this vulnerability being exploited, the team wants to modify the software requirements to disallow users from entering HTML as input into their Web application. What kind of Web application vulnerability likely exists in their software?
Options
- ACross-site scripting vulnerability
- BSession management vulnerability
- CSQL injection vulnerability
- DCross-site Request Forgery vulnerability
How the community answered
(55 responses)- A95% (52)
- B4% (2)
- D2% (1)
Why each option
Allowing raw HTML input in a web application creates a cross-site scripting (XSS) vulnerability, enabling attackers to inject malicious scripts executed in other users' browsers.
Cross-site scripting (XSS) occurs when a web application accepts unescaped or unsanitized HTML and JavaScript from user input and renders it in the browser of another user. Attackers exploit this by injecting script tags or event handlers that execute in the victim's browser session, potentially stealing cookies or credentials. Disallowing HTML input or encoding it before rendering is the primary mitigation for reflected and stored XSS attacks.
Session management vulnerabilities involve improper handling of session tokens, insecure cookies, or session fixation - not the acceptance of HTML markup as user input.
SQL injection involves inserting malicious SQL syntax into database queries through input fields, not injecting HTML markup into web page content.
Cross-site Request Forgery (CSRF) exploits an authenticated user's session to submit unauthorized requests to a trusted site, and is not related to accepting HTML as user input.
Concept tested: Cross-site scripting (XSS) via unsanitized HTML input
Source: https://owasp.org/www-community/attacks/xss/
Topics
Community Discussion
No community discussion yet for this question.