Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

Filling Out Forms: Still a Dangerous Game

Despite upgrades and fixes, most browsers are still vulnerable to attacks via Web forms, researcher says

It may not sound too scary, but filling out forms on the Web is still a dicey business, a researcher said this week.

In an update of his 2002 paper, which exposed many of the vulnerabilities associated with HTML forms, EnableSecurity's Sandro Gauci states that most browsers still haven't completely fixed the problems associated with commonly used forms.

"Does it still work? The short answer is yes," Gauci says in the updated paper. "Most popular Web browsers seem to block certain well-known ports. However, there are many cases where an attacker can make use of ports which are not on the blacklist." And Internet Explorer and Opera don't block as many ports as Safari or Firefox, he says.

The problem, in part, is that most browsers do their best to render any data they receive in HTML, Gauci explains. While the browser vendors have generally shored up the vulnerabilities in Web forms that are exchanged with an HTML server, most of them have done little about the exchange of forms between a browser and a non-HTTP server, such as an FTP or SMTP server.

Since the browser has no way of distinguishing between an HTTP server and a non-HTTP server, a user might be enticed to browse to a non-HTTP server, which would typically send an error message to the browser, the paper says. But a wily hacker might be able to attach malicious code to the error message, and potentially launch a cross-site scripting (XSS) attack or steal data from the browser that would allow him to gain access to the user's information or take over the user's machine. .

"When an attacker can control what is returned by the server, the victim becomes vulnerable to security issues such as [XSS]," Gauci writes. "In the case of HTTP servers, this is a well-known issue, and therefore modern Web servers do not exhibit this behavior by default.

"However, this is not the case with other kinds of servers, such as SMTP or FTP servers, [which] often echo back error messages containing user input," the paper observes. "When this user input can be controlled by the attacker, bad things can happen."

To repair the vulnerability, browser vendors will need to re-tool their browsers so that they do not attempt to render responses from non-HTTP servers in HTML, Gauci says.

"One solution would be to check the HTTP response headers and make sure that they are indeed HTTP 1.0 or 1.1-compliant," he says. "This would identify IMAP or FTP servers responding with malicious HTML. When the HTTP response headers are not found, the Web browser should not render the content as HTML."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31922
PUBLISHED: 2021-05-14
An HTTP Request Smuggling vulnerability in Pulse Secure Virtual Traffic Manager before 21.1 could allow an attacker to smuggle an HTTP request through an HTTP/2 Header. This vulnerability is resolved in 21.1, 20.3R1, 20.2R1, 20.1R2, 19.2R4, and 18.2R3.
CVE-2021-32051
PUBLISHED: 2021-05-14
Hexagon G!nius Auskunftsportal before 5.0.0.0 allows SQL injection via the GiPWorkflow/Service/DownloadPublicFile id parameter.
CVE-2021-32615
PUBLISHED: 2021-05-13
Piwigo 11.4.0 allows admin/user_list_backend.php order[0][dir] SQL Injection.
CVE-2021-33026
PUBLISHED: 2021-05-13
The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the ca...
CVE-2021-31876
PUBLISHED: 2021-05-13
Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the replacement policy specified in BIP125, which makes it easier for attackers to trigger a loss of funds, or a denial of service attack against downstream projects such as Lightning network nodes. An unconfirmed child transaction with ...