GitStack up to 2.3.10 rest/user/ username/password User input validation

Summaryinfo

A vulnerability has been found in GitStack up to 2.3.10 and classified as critical. This vulnerability affects unknown code of the file rest/user/. Performing a manipulation of the argument username/password results in input validation (User). This vulnerability is cataloged as CVE-2018-5955. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in GitStack up to 2.3.10. This affects an unknown part of the file rest/user/. The manipulation of the argument username/password with an unknown input leads to a input validation vulnerability (User). CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in GitStack through 2.3.10. User controlled input is not sufficiently filtered, allowing an unauthenticated attacker to add a user to the server via the username and password fields to the rest/user/ URI.

The bug was discovered 01/15/2018. The weakness was shared 01/21/2018 (Website). The advisory is shared at blogs.securiteam.com. This vulnerability is uniquely identified as CVE-2018-5955 since 01/21/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.

The exploit is shared for download at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k.

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 (44044). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• GitStack

Version

• 2.3.0
• 2.3.1
• 2.3.2
• 2.3.3
• 2.3.4
• 2.3.5
• 2.3.6
• 2.3.7
• 2.3.8
• 2.3.9
• 2.3.10

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