Muviko 1.1 login.php ID sql injection

Summaryinfo

A vulnerability identified as critical has been detected in Muviko 1.1. This impacts an unknown function of the file login.php. Performing a manipulation of the argument ID as part of Parameter results in sql injection. This vulnerability was named CVE-2017-17970. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in Muviko 1.1. It has been classified as critical. This affects some unknown functionality of the file login.php. The manipulation of the argument id as part of a Parameter leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Multiple SQL injection vulnerabilities in Muviko 1.1 allow remote attackers to execute arbitrary SQL commands via the (1) email parameter to login.php; the (2) season_id parameter to themes/flixer/ajax/load_season.php; the (3) movie_id parameter to themes/flixer/ajax/get_rating.php; the (4) rating or (5) movie_id parameter to themes/flixer/ajax/update_rating.php; or the (6) id parameter to themes/flixer/ajax/set_player_source.php.

The bug was discovered 01/11/2018. The weakness was presented 01/12/2018 (Website). The advisory is shared at packetstormsecurity.com. This vulnerability is uniquely identified as CVE-2017-17970 since 12/29/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is shared for download 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 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:login.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 vulnerability database at Exploit-DB (43477). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Muviko

Version

• 1.1

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion