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
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Russian Military Officers Unmasked, Indicted for High-Profile Cyberattack Campaigns
Kelly Jackson Higgins, Executive Editor at Dark Reading,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7751
PUBLISHED: 2020-10-26
This affects all versions of package pathval.
CVE-2020-27678
PUBLISHED: 2020-10-26
An issue was discovered in illumos before 2020-10-22, as used in OmniOS before r151030by, r151032ay, and r151034y and SmartOS before 20201022. There is a buffer overflow in parse_user_name in lib/libpam/pam_framework.c.
CVE-2020-27388
PUBLISHED: 2020-10-23
Multiple Stored Cross Site Scripting (XSS) vulnerabilities exist in the YOURLS Admin Panel, Versions 1.5 - 1.7.10. An authenticated user must modify a PHP plugin with a malicious payload and upload it, resulting in multiple stored XSS issues.
CVE-2020-24847
PUBLISHED: 2020-10-23
A Cross-Site Request Forgery (CSRF) vulnerability is identified in FruityWifi through 2.4. Due to a lack of CSRF protection in page_config_adv.php, an unauthenticated attacker can lure the victim to visit his website by social engineering or another attack vector. Due to this issue, an unauthenticat...
CVE-2020-24848
PUBLISHED: 2020-10-23
FruityWifi through 2.4 has an unsafe Sudo configuration [(ALL : ALL) NOPASSWD: ALL]. This allows an attacker to perform a system-level (root) local privilege escalation, allowing an attacker to gain complete persistent access to the local system.