phpMyRecipes 1.2.2 dosearch.php words_exact sql injection

Summaryinfo

A vulnerability was found in phpMyRecipes 1.2.2. It has been declared as critical. The affected element is an unknown function of the file dosearch.php. Executing a manipulation of the argument words_exact can lead to sql injection. This vulnerability is handled as CVE-2014-9347. The attack can be executed remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability has been found in phpMyRecipes 1.2.2 and classified as critical. This vulnerability affects some unknown processing of the file dosearch.php. The manipulation of the argument words_exact with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

SQL injection vulnerability in dosearch.php in phpMyRecipes 1.2.2 allows remote attackers to execute arbitrary SQL commands via the words_exact parameter.

The weakness was released 12/08/2014 (Website). The advisory is shared for download at xforce.iss.net. This vulnerability was named CVE-2014-9347 since 12/08/2014. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.

A public exploit has been developed by bard and been published even before and not after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 13 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:dosearch.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (99005), Exploit-DB (35365) and OSVDB (115038†). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• phpMyRecipes

Version

• 1.2.2

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion