SLiMS 8 Akasia up to 8.3.1 app_user.php cross-site request forgery

Summaryinfo

A vulnerability, which was classified as problematic, has been found in SLiMS 8 Akasia up to 8.3.1. This impacts an unknown function of the file admin/modules/system/app_user.php. The manipulation leads to cross-site request forgery. This vulnerability is documented as CVE-2017-12584. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in SLiMS 8 Akasia up to 8.3.1. This issue affects an unknown functionality of the file admin/modules/system/app_user.php. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:

There is no CSRF mitigation in SLiMS 8 Akasia through 8.3.1. Also, an entire user profile (including the password) can be updated without sending the current password. This allows remote attackers to trick a user into changing to an attacker-controlled password, a complete account takeover, via the passwd1 and passwd2 fields in an admin/modules/system/app_user.php changecurrent=true operation.

The bug was discovered 05/26/2017. The weakness was released 08/06/2017 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2017-12584 since 08/05/2017. 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 are known, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 71 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:admin/modules/system/app_user.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.

Entries connected to this vulnerability are available at VDB-104863 and VDB-104862. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• SLiMS 8 Akasia

Version

• 8.3.0
• 8.3.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