BlogoText up to 3.7.6 admin/maintenance.php creer_fichier_zip Filename information disclosure

Summaryinfo

A vulnerability identified as problematic has been detected in BlogoText up to 3.7.6. This affects the function creer_fichier_zip of the file admin/maintenance.php. This manipulation as part of Filename causes information disclosure. This vulnerability appears as CVE-2017-17793. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in BlogoText up to 3.7.6. It has been declared as problematic. Affected by this vulnerability is the function creer_fichier_zip of the file admin/maintenance.php. The manipulation as part of a Filename leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

Information Disclosure vulnerability in creer_fichier_zip in admin/maintenance.php in BlogoText through 3.7.6 allows remote attackers to defeat a filename-randomization protection mechanism, and read backup archives on Windows servers, by providing the archiv~1.zip name (aka an 8.3 filename).

The bug was discovered 11/17/2017. The weakness was presented 12/20/2017 (GitHub Repository). The advisory is shared at github.com. This vulnerability is known as CVE-2017-17793 since 12/20/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

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

See VDB-110834 and VDB-110832 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• BlogoText

Version

• 3.7.0
• 3.7.1
• 3.7.2
• 3.7.3
• 3.7.4
• 3.7.5
• 3.7.6

License

• open-source

Website

• Product: https://github.com/BlogoText/blogotext/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion