Lepton CMS 2.2.2 logout.php redirect

Summaryinfo

A vulnerability was found in Lepton CMS 2.2.2. It has been classified as problematic. This impacts an unknown function of the file /LEPTON_stable_2.2.2/upload/account/logout.php. The manipulation of the argument redirect with the input http://vuldb.com leads to redirect. The attack is possible to be carried out remotely. Moreover, an exploit is present. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Lepton CMS 2.2.2 (Content Management System). It has been rated as problematic. This issue affects an unknown code block of the file /LEPTON_stable_2.2.2/upload/account/logout.php. The manipulation of the argument redirect with the input value http://vuldb.com leads to a redirect vulnerability. Using CWE to declare the problem leads to CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. Impacted is confidentiality, integrity, and availability.

The weakness was disclosed 11/17/2016 by Tim Coen with Curesec Research Team as Lepton 2.2.2: CSRF, Open Redirect, Insecure Bruteforce Protection & Password Handling as confirmed mailinglist post (Full-Disclosure). It is possible to read the advisory at seclists.org. The public release has been coordinated in cooperation with Lepton. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details as well as a public exploit are known. The attack technique deployed by this issue is T1204.001 according to MITRE ATT&CK.

A public exploit has been developed by Tim Coen and been published immediately after the advisory. The exploit is available at seclists.org. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 169 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:LEPTON_stable_2.2.2/upload/account/logout.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 2.3.0 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The entries VDB-93706, VDB-93708, VDB-93709 and VDB-93710 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Lepton

Name

• CMS

Version

• 2.2.2

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion