Contents
- Vital information on this issue
- Scanning For and Finding Vulnerabilities in Custom Web Code
- Penetration Testing (Pentest) for this Vulnerability
- Security updates on Vulnerabilities in Custom Web Code
- Disclosures related to Vulnerabilities in Custom Web Code
- Confirming the Presence of Vulnerabilities in Custom Web Code
- False positive/negatives
- Patching/Repairing this vulnerability
- Exploits related to Vulnerabilities in Custom Web Code
Vital Information on This Issue
Vulnerabilities in Custom Web Code is a high risk vulnerability that is one of the most frequently found on networks around the world. This issue has been around since at least 1990 but has proven either difficult to detect, difficult to resolve or prone to being overlooked entirely.
| Vulnerability Name: | Custom Web Code |
| Test ID: | 2062 |
| Risk: | High |
| Category: | Server-Side Scripts |
| Type: | Attack |
| Summary: | We discovered vulnerabilities in the scripts listed below. Next to each script, there is a description of the type of attack that is possible, and the way to recreate the attack. If the attack is a simple HTTP GET request, you can usually paste it into your browser to see how it works. If it’s a POST attack, the parameters for the POST request will be listed in square parenthesis. |
| Impact: | Attackers can take control over your database, and in some cases over the operating system (using master..xp_cmdshell, CREATE LIBRARY, etc). |
| Solution: | * SQL Injection: Use stored procedures to prevent attackers from altering the queries, and filter user input to discard invalid characters such as ‘ * Cross Site Scripting: Filter user input to discard characters such as < and >. Make sure your server does not display error messages that contain input received from the user. * Source Disclosure: Make sure all debugging information is turned off from production servers. Scripts should be configured to be executables only, with no ability for a user to view them. * Non-SSL login: All login pages should be SSL protected (e.g. have an https:// link). When using non-SSL protected pages eavesdroppers might be able to capture usernames and passwords * Sensitive information sent over non-encrypted page: Make sure all sensitive information is sent over SSL-protected pages. |
| CVE: | N/A |
| More Information: | https://support.microsoft.com/en-us/kb/814869 https://www.owasp.org/index.php/Guide_to_SQL_Injection https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet |
| Nist NVD (CVSS): | N/A |
| CVSS Score: | N/A |
| Microsoft Knowledge Base: | 302570 |
Scanning For and Finding Vulnerabilities in Custom Web Code
Use of Vulnerability Management tools, like AVDS, are standard practice for the discovery of this vulnerability. The primary failure of VA in finding this vulnerability is related to setting the proper scope and frequency of network scans. It is vital that the broadest range of hosts (active IPs) possible are scanned and that scanning is done frequently. We recommend weekly. Your existing scanning solution or set of test tools should make this not just possible, but easy and affordable. If that is not the case, please consider AVDS.
Penetration Testing (pentest) for this Vulnerability
The Vulnerabilities in Custom Web Code is prone to false positive reports by most vulnerability assessment solutions. AVDS is alone in using behavior based testing that eliminates this issue. For all other VA tools security consultants will recommend confirmation by direct observation. In any case Penetration testing procedures for discovery of Vulnerabilities in Custom Web Code produces the highest discovery accuracy rate, but the infrequency of this expensive form of testing degrades its value. The ideal would be to have pentesting accuracy and the frequency and scope possibilities of VA solutions, and this is accomplished only by AVDS.
Security Updates on Vulnerabilities in Custom Web Code
Given that this is one of the most frequently found vulnerabilities, there is ample information regarding mitigation online and very good reason to get it fixed. Hackers are also aware that this is a frequently found vulnerability and so its discovery and repair is that much more important. It is so well known and common that any network that has it present and unmitigated indicates “low hanging fruit” to attackers.
Disclosures related to this vulnerability
Confirming the Presence of Vulnerabilities in Custom Web Code
AVDS is currently testing for and finding this vulnerability with zero false positives. If your current set of tools is indicating that it is present but you think it is probably a false positive, please contact us for a demonstration of AVDS.
False positive/negatives
The secret killer of VA solution value is the false positive. There was an industry wide race to find the most vulnerabilities, including Vulnerabilities in Custom Web Code ,and this resulted in benefit to poorly written tests that beef up scan reports by adding a high percentage of uncertainty. This may have sold a lot of systems some years ago, but it also stuck almost all VA solutions with deliberately inaccurate reporting that adds time to repairs that no administrator can afford. Beyond Security did not participate in this race to mutually assured destruction of the industry and to this day produces the most accurate and actionable reports available.
Patching/Repairing this Vulnerability
https://www.owasp.org/index.php/Virtual_Patching_Cheat_Sheet Vulnerabilities in Custom Web Code is a high risk vulnerability that is also high frequency and high visibility. This is the most severe combination of security factors that exists and it is extremely important to find it on your network and fix it as soon as possible.
Exploits related to Vulnerabilities in Custom Web Code
https://www.whitehatsec.com/articles/mythbusting_buffer_overflow.shtml
http://blog.templatetoaster.com/top-8-website-vulnerabilities-hacker-can-exploit/